From: Soft Works <softworkz@hotmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: softworkz <ffmpegagent@gmail.com>
Subject: Re: [FFmpeg-devel] [PATCH] Update ReadMe.md for PR submission and reference Developer Documentation
Date: Wed, 25 May 2022 08:24:45 +0000
Message-ID: <DM8P223MB036539D79CE1391FF2D4FE24BAD69@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CAPYw7P6kf1nfFyD1CPX1PjLE=j9Vht5=2p2678CM3vOikqpWiQ@mail.gmail.com>
> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Paul B
> Mahol
> Sent: Wednesday, May 25, 2022 9:30 AM
> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Cc: softworkz <ffmpegagent@gmail.com>
> Subject: Re: [FFmpeg-devel] [PATCH] Update ReadMe.md for PR submission and
> reference Developer Documentation
>
> On Wed, May 25, 2022 at 2:24 AM Soft Works <softworkz@hotmail.com> wrote:
>
> >
> >
> > > -----Original Message-----
> > > From: softworkz <ffmpegagent@gmail.com>
> > > Sent: Thursday, February 3, 2022 10:28 PM
> > > To: ffmpeg-devel@ffmpeg.org
> > > Cc: softworkz <softworkz@hotmail.com>; softworkz
> <softworkz@hotmail.com>
> > > Subject: [PATCH] Update ReadMe.md for PR submission and reference
> > > Developer Documentation
> > >
> > > From: softworkz <softworkz@hotmail.com>
> > >
> > > Signed-off-by: softworkz <softworkz@hotmail.com>
> > > ---
> > > Update ReadMe.md for PR submission and reference Developer
> > > Documentation
> > >
> > > .
> > >
> > > Published-As: https://github.com/ffstaging/FFmpeg/releases/tag/pr-
> > > ffstaging-22%2Fsoftworkz%2Fpatch-2-v1
> > > Fetch-It-Via: git fetch https://github.com/ffstaging/FFmpeg
> > pr-ffstaging-
> > > 22/softworkz/patch-2-v1
> > > Pull-Request: https://github.com/ffstaging/FFmpeg/pull/22
> > >
> > > README.md | 18 ++++++++++++++++--
> > > 1 file changed, 16 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/README.md b/README.md
> > > index f8c23f2870..07f717a4f9 100644
> > > --- a/README.md
> > > +++ b/README.md
> > > @@ -41,6 +41,20 @@ GPL. Please refer to the LICENSE file for detailed
> > > information.
> > >
> > > ## Contributing
> > >
> > > +### Mailing List
> > > +
> > > Patches should be submitted to the ffmpeg-devel mailing list using
> > > -`git format-patch` or `git send-email`. Github pull requests should
> be
> > > -avoided because they are not part of our review process and will be
> > > ignored.
> > > +`git format-patch` or `git send-email` as described in the
> > > +[Developer
> > > Documentation](https://www.ffmpeg.org/developer.html#Contributing).
> > > +
> > > +### Pull Requests
> > > +
> > > +There is a new experimental way that allows submitting Pull Requests
> > > +and having them forwarded to the ffmpeg Mailing List.
> > > +
> > > +Please submit your Pull Requests here:
> > > **https://github.com/ffstaging/FFmpeg**.
> > > +
> > > +Then, follow the instructions from the automatic CodeBot response.
> > > +Besides the submission procedure, the
> > > +[Developer
> > > Documentation](https://www.ffmpeg.org/developer.html#Contributing)
> > > +applies in the same way like when submitting to the ML directly.
> > >
> > > base-commit: e1a14479a81f5366b95df543992a7fe637cf2dde
> > > --
> > > ffmpeg-codebot
> >
> >
> > Does anybody have objections regarding this doc change?
> >
>
> I have.
Ok, that's fine. I really don't want to fight for this, just cleanup my
my list a bit, so I'll close it then.
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".
prev parent reply other threads:[~2022-05-25 8:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 21:28 softworkz
2022-05-25 0:24 ` Soft Works
2022-05-25 7:30 ` Paul B Mahol
2022-05-25 8:24 ` Soft Works [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=DM8P223MB036539D79CE1391FF2D4FE24BAD69@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
--to=softworkz@hotmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=ffmpegagent@gmail.com \
/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