Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "softworkz ." <softworkz-at-hotmail.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 2/2] fftools/ffmpeg_filter: make InputFilterPriv and OutputFilterPriv private again
Date: Mon, 2 Jun 2025 02:46:01 +0000
Message-ID: <DM8P223MB0365CAB857987890930A1178BA62A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <e7178846-7ae4-4d9b-95ef-322160269bc7@gmail.com>



> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of James Almer
> Sent: Montag, 2. Juni 2025 04:41
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH 2/2] fftools/ffmpeg_filter: make
> InputFilterPriv and OutputFilterPriv private again
> 
> On 6/1/2025 11:07 PM, softworkz . wrote:
> >
> >
> >> -----Original Message-----
> >> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of softworkz
> .
> >> Sent: Samstag, 31. Mai 2025 03:44
> >> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> >> Subject: Re: [FFmpeg-devel] [PATCH 2/2] fftools/ffmpeg_filter: make
> >> InputFilterPriv and OutputFilterPriv private again
> >
> > [..]
> >
> >> 7 lines further down, there's another change needed:
> >>
> >>
> >>          if (ofilter->output_name && ofilter->filter)
> >>              av_dict_set(&output_map, ofilter->filter->name, ofilter-
> >>> output_name, 0);
> >>
> >>
> >> This is what broke the graph connections on the output side.
> >>
> >> Thanks
> >> sw
> >>
> >> _______________________________________________
> >
> >
> > Hello James,
> >
> > I have seen you already pushed this.
> >
> > What I would like to note is that you could have just asked me
> > and I would have done it myself. This goes without saying.
> 
> I pushed the set because i authored it. No point asking someone else to
> do it. I did however forget to send a reply acknowledging your review
> and LGTM before pushing it.

Oh, sorry for the misunderstanding.

I wasn't talking about pushing. I was talking about doing the 
work you did in this patchset.

When my changes did something that should have been done 
differently, then it's my responsibility to get it right.
(unless somebody really wants to do it).

In this regard I'm always open to talk about, because the least
thing I want is to cause additional work for others.

Best,
sw

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

  reply	other threads:[~2025-06-02  2:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-29  3:06 [FFmpeg-devel] [PATCH 1/2] fftools/ffmpeg_filter: make FilterGraphPriv " James Almer
2025-05-29  3:06 ` [FFmpeg-devel] [PATCH 2/2] fftools/ffmpeg_filter: make InputFilterPriv and OutputFilterPriv " James Almer
2025-05-31  0:49   ` softworkz .
2025-05-31  1:44   ` softworkz .
2025-06-02  2:07     ` softworkz .
2025-06-02  2:40       ` James Almer
2025-06-02  2:46         ` softworkz . [this message]
2025-06-02  2:57         ` softworkz .
2025-05-29  3:16 ` [FFmpeg-devel] [PATCH 1/2] fftools/ffmpeg_filter: make FilterGraphPriv " softworkz .
2025-05-31  1:42 ` softworkz .

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DM8P223MB0365CAB857987890930A1178BA62A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
    --to=softworkz-at-hotmail.com@ffmpeg.org \
    --cc=ffmpeg-devel@ffmpeg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git