| Message ID | pull.22.ffstaging.FFmpeg.1643923701194.ffmpegagent@gmail.com |
|---|---|
| State | New |
| Headers | show |
| Series | [FFmpeg-devel] Update ReadMe.md for PR submission and reference Developer Documentation | expand |
| Context | Check | Description |
|---|---|---|
| andriy/commit_msg_aarch64_jetson | warning | The first line of the commit message must start with a context terminated by a colon and a space, for example "lavu/opt: " or "doc: ". |
| andriy/commit_msg_armv7_RPi4 | warning | The first line of the commit message must start with a context terminated by a colon and a space, for example "lavu/opt: " or "doc: ". |
| andriy/make_aarch64_jetson | success | Make finished |
| andriy/make_fate_aarch64_jetson | success | Make fate finished |
| andriy/make_armv7_RPi4 | success | Make finished |
| andriy/make_fate_armv7_RPi4 | success | Make fate finished |
| andriy/commit_msg_x86 | warning | The first line of the commit message must start with a context terminated by a colon and a space, for example "lavu/opt: " or "doc: ". |
| andriy/make_x86 | success | Make finished |
| andriy/make_fate_x86 | success | Make fate finished |
| andriy/commit_msg_ppc | warning | The first line of the commit message must start with a context terminated by a colon and a space, for example "lavu/opt: " or "doc: ". |
| andriy/make_ppc | success | Make finished |
| andriy/make_fate_ppc | success | Make fate finished |
> -----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? Thanks, sw
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. > > Thanks, > 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". >
> -----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
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.