Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Leo Izen <leo.izen@gmail.com>
To: FFmpeg Development Discussions and Patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] doc/examples/muxing: code rewrite with improved readability and fixed issues
Date: Sun, 19 Jun 2022 17:21:54 -0400
Message-ID: <734e1556-f296-7dae-970b-e31c182cc525@gmail.com> (raw)
In-Reply-To: <1429832117.8300123.1655600743317@mail.yahoo.com>


On 6/18/22 21:05, Paolo Prete wrote:
> A new patch is attached to this mail.

Don't forget to add -v2 to your git format-patch line, which changes the 
patch header so it says [PATCH v2], which makes it easier for other 
readers to keep track of things. Also, it's usually a good idea to 
provide a shortlist of what changed in the new patch to help out
reviewers.

- Leo Izen (thebombzen)
_______________________________________________
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:[~2022-06-19 21:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <122266341.9130638.1655553986479.ref@mail.yahoo.com>
2022-06-18 12:06 ` Paolo Prete
2022-06-18 15:17   ` Leo Izen
2022-06-19  0:25     ` Paolo Prete
     [not found]       ` <985091997.9345851.1655600194188@mail.yahoo.com>
2022-06-19  1:05         ` Paolo Prete
2022-06-19 21:21           ` Leo Izen [this message]
2022-06-18 17:08   ` Andreas Rheinhardt
2022-06-19  0:39     ` Paolo Prete

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=734e1556-f296-7dae-970b-e31c182cc525@gmail.com \
    --to=leo.izen@gmail.com \
    --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