From: Soft Works <softworkz@hotmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] GitHub Integration
Date: Sat, 25 Dec 2021 16:23:53 +0000
Message-ID: <DM8P223MB0365281EDFC1D913AD804A10BA409@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CABiDpkmrJ=sLagwNo5PZxES4s+u9Fg1ftH6dwL+W-G_hLqgM_A@mail.gmail.com>
> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Vasily
> Sent: Saturday, December 25, 2021 10:32 AM
> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] GitHub Integration
>
> Hi,
>
> First off, a great idea bridging that gap! But I agree that the topic is
> misleading, maybe rename to smth like "github bridge for PR creation" to be
> really explicit?
Agreed. Once I start another conversation for the next step, I'll try to
choose a better subject.
> Second one, why first-comers aren't allowed to submit without pre-approval?
> (context: I haven't made my contributions to ffmpeg yet, though posted a
> single patch which stalled at review because of lack of my time).
Ah yes, that's a good question. When we had discussed this back in August,
there were concerns that this might cause a certain amount of hoax-, nonsense-
or low-quality patches to hit the mailing list.
And that's what it's about. The "pre-approval" for first-posters is not
meant to be a review. Reviews are done on the mailing list, just like usual.
This is intended to a rather low bar and all that an "already allowed" user
is expected to do is to take a very quick look at the submitted PR, whether
it _appears_ to be a reasonable contribution.
> And last point - if comments from github aren't re-posted to the list,
> maybe the boy should remove them or edit by removing the message and
> telling the commenter to use the ML?
Messages from the ML which are shown on GitHub are always including a
"Reply-To" link with instruction about how to reply.
> Anyway, good idea!
Drop me a note, then I'll send you the link where you can try it out.
Regards,
softworkz
_______________________________________________
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".
next prev parent reply other threads:[~2021-12-25 16:24 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 23:24 Soft Works
2021-12-23 7:35 ` Paul B Mahol
2021-12-23 8:10 ` Soft Works
2021-12-23 13:59 ` Tomas Härdin
2021-12-23 14:08 ` Soft Works
2021-12-23 14:16 ` Timo Rothenpieler
2021-12-23 20:50 ` Soft Works
2021-12-23 22:30 ` Soft Works
2021-12-25 9:31 ` Vasily
2021-12-25 9:33 ` Vasily
2021-12-25 11:12 ` Michael Niedermayer
2021-12-25 16:27 ` Soft Works
2021-12-25 16:23 ` Soft Works [this message]
2021-12-25 16:50 ` Lynne
2021-12-25 17:15 ` Soft Works
2021-12-26 0:54 ` lance.lmwang
2021-12-26 1:03 ` Steven Liu
2021-12-26 16:48 ` Lynne
2021-12-26 20:21 ` Soft Works
2021-12-26 21:37 ` Ronald S. Bultje
2021-12-26 23:10 ` Soft Works
2021-12-27 1:41 ` lance.lmwang
2021-12-27 14:59 ` Zane van Iperen
2021-12-27 15:36 ` Vasily
2021-12-28 21:21 ` Niklas Haas
2021-12-28 21:57 ` Soft Works
2022-01-02 3:28 ` Soft Works
2022-01-02 14:04 ` Lynne
2022-01-02 18:16 ` Soft Works
2022-01-21 1:29 ` Soft Works
2021-12-29 19:57 ` Anton Khirnov
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=DM8P223MB0365281EDFC1D913AD804A10BA409@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
--to=softworkz@hotmail.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