| Message ID | MN2PR04MB59817F7A5B692B05ACAE1D2EBAF49@MN2PR04MB5981.namprd04.prod.outlook.com |
|---|---|
| State | Superseded, archived |
| Headers | show |
| Series | [FFmpeg-devel,v2] doc/developer: Add description about safely sending patches via E-Mail clients | expand |
| Context | Check | Description |
|---|---|---|
| andriy/x86_make | success | Make finished |
| andriy/x86_make_fate | success | Make fate finished |
| andriy/PPC64_make | success | Make finished |
| andriy/PPC64_make_fate | success | Make fate finished |
Soft Works: > (v2: fix doc build) This should be directly after the --- below. > > Signed-off-by: softworkz <softworkz@hotmail.com> > --- > doc/developer.texi | 16 ++++++++++++++++ > 1 file changed, 16 insertions(+) > > diff --git a/doc/developer.texi b/doc/developer.texi > index b33cab0fc7..ce5500b85d 100644 > --- a/doc/developer.texi > +++ b/doc/developer.texi > @@ -494,6 +494,22 @@ patch is inline or attached per mail. > You can check @url{https://patchwork.ffmpeg.org}, if your patch does not show up, its mime type > likely was wrong. > > +@subheading Sending E-Mail Client - Example for MS Outlook. > +Using @code{git send-email} might not be desirable for everyone. The > +following trick allows to send patches via E-Mail clients in a safe > +way. It has been tested with Outlook and Thunderbird (with X-Unsent > +extension) and might work with other applications. > + > +Create your patch like this: > + > +@verbatim > +git format-patch -s -o "outputfolder" --add-header "X-Unsent: 1" --suffix .eml --to ffmpeg-devel@ffmpeg.org -1 1a2b3c4d > +@end verbatim > + > +Now you'll just need to open the eml file with the E-Mail application > +and execure 'Send'. I guess this is supposed to be execute. > + > +@subheading Reviews. > Your patch will be reviewed on the mailing list. You will likely be asked > to make some changes and are expected to send in an improved version that > incorporates the requests from the review. This process may go through >
> -----Original Message----- > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of > Andreas Rheinhardt > Sent: Saturday, 7 August 2021 13:51 > To: ffmpeg-devel@ffmpeg.org > Subject: Re: [FFmpeg-devel] [PATCH v2] doc/developer: Add description > about safely sending patches via E-Mail clients > > Soft Works: > > (v2: fix doc build) > > This should be directly after the --- below. Thanks for the hint. This mailing list thing is not my world ;-) > > > > Signed-off-by: softworkz <softworkz@hotmail.com> > > --- > > doc/developer.texi | 16 ++++++++++++++++ > > 1 file changed, 16 insertions(+) > > > > diff --git a/doc/developer.texi b/doc/developer.texi index > > b33cab0fc7..ce5500b85d 100644 > > --- a/doc/developer.texi > > +++ b/doc/developer.texi > > @@ -494,6 +494,22 @@ patch is inline or attached per mail. > > You can check @url{https://patchwork.ffmpeg.org}, if your patch does > > not show up, its mime type likely was wrong. > > > > +@subheading Sending E-Mail Client - Example for MS Outlook. > > +Using @code{git send-email} might not be desirable for everyone. The > > +following trick allows to send patches via E-Mail clients in a safe > > +way. It has been tested with Outlook and Thunderbird (with X-Unsent > > +extension) and might work with other applications. > > + > > +Create your patch like this: > > + > > +@verbatim > > +git format-patch -s -o "outputfolder" --add-header "X-Unsent: 1" > > +--suffix .eml --to ffmpeg-devel@ffmpeg.org -1 1a2b3c4d @end verbatim > > + > > +Now you'll just need to open the eml file with the E-Mail application > > +and execure 'Send'. > > I guess this is supposed to be execute. Good eye! Thanks for reviewing. Update sent. sw
diff --git a/doc/developer.texi b/doc/developer.texi index b33cab0fc7..ce5500b85d 100644 --- a/doc/developer.texi +++ b/doc/developer.texi @@ -494,6 +494,22 @@ patch is inline or attached per mail. You can check @url{https://patchwork.ffmpeg.org}, if your patch does not show up, its mime type likely was wrong. +@subheading Sending E-Mail Client - Example for MS Outlook. +Using @code{git send-email} might not be desirable for everyone. The +following trick allows to send patches via E-Mail clients in a safe +way. It has been tested with Outlook and Thunderbird (with X-Unsent +extension) and might work with other applications. + +Create your patch like this: + +@verbatim +git format-patch -s -o "outputfolder" --add-header "X-Unsent: 1" --suffix .eml --to ffmpeg-devel@ffmpeg.org -1 1a2b3c4d +@end verbatim + +Now you'll just need to open the eml file with the E-Mail application +and execure 'Send'. + +@subheading Reviews. Your patch will be reviewed on the mailing list. You will likely be asked to make some changes and are expected to send in an improved version that incorporates the requests from the review. This process may go through
(v2: fix doc build) Signed-off-by: softworkz <softworkz@hotmail.com> --- doc/developer.texi | 16 ++++++++++++++++ 1 file changed, 16 insertions(+)