Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Tomas Härdin" <tjoppen@acc.umu.se>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v4 1/1] avformat: Add IPFS protocol support.
Date: Sat, 12 Feb 2022 12:58:12 +0100
Message-ID: <082d3be259f0e24332ef3641813e696844411433.camel@acc.umu.se> (raw)
In-Reply-To: <CAPd6JnHLALf3m0GJi=Ooafx0vjDGWLYZgiWop8+58gZo2A+92Q@mail.gmail.com>

ons 2022-02-09 klockan 18:36 +0100 skrev Mark Gaiser:
> > 
> Thank you so much for all the valuable feedback! It's much
> appreciated :)
> 
> I'll fix all the still open issues and send another patch mail
> somewhere
> later this week.
> Question though, as this seems to be heading towards the final patch
> version. How do you prefer to see the next patch round?
> 
> 1. As it's done currently. You don't see what's different.
> 2. As a 1/2 and 2/2 patch where 2/2 would be the a diff on top of 1/2
> with
> the review feedback applied.
> 
> Either is fine with me.
> But I fear that a split patch mail (so 1/2 with the code as is right
> now
> and 2/2 with the feedback changes) could potentially waste people's
> time if
> they comment on something that is fixed in the feedback patch.

Submit patches as you want them in the source tree. Writing patches to
patches not yet committed makes little sense.

/Tomas

_______________________________________________
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".

      parent reply	other threads:[~2022-02-12 11:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-03 17:29 [FFmpeg-devel] [PATCH v4 0/1] " Mark Gaiser
2022-02-03 17:29 ` [FFmpeg-devel] [PATCH v4 1/1] avformat: " Mark Gaiser
2022-02-04 11:10   ` Tomas Härdin
2022-02-04 14:12     ` Mark Gaiser
2022-02-07 15:09       ` Tomas Härdin
2022-02-09 17:36         ` Mark Gaiser
2022-02-10  1:14           ` Mark Gaiser
2022-02-12 11:58           ` Tomas Härdin [this message]

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=082d3be259f0e24332ef3641813e696844411433.camel@acc.umu.se \
    --to=tjoppen@acc.umu.se \
    --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