Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] GitHub Integration
Date: Sat, 25 Dec 2021 12:12:02 +0100
Message-ID: <20211225111202.GT2829255@pb2> (raw)
In-Reply-To: <CABiDpkmrJ=sLagwNo5PZxES4s+u9Fg1ftH6dwL+W-G_hLqgM_A@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1018 bytes --]

On Sat, Dec 25, 2021 at 12:31:56PM +0300, Vasily wrote:
> 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?
> 

> Second one, why first-comers aren't allowed to submit without pre-approval?

Some pull requests on github where "spam" iam not sure how exactly these happen
maybe someoen pressing the wrong buttons, or someone not understanding github
pull requests for random branches like for example our release branch onto
master or something like this has been submitted IIRC. On github its a matter
of closing the request, but if that resulted in a post to the ML it could
produce hundreads of mails. So some sort of pre-approval or some other sort
of double check that a submissing is intended is required

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

No snowflake in an avalanche ever feels responsible. -- Voltaire

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
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".

  parent reply	other threads:[~2021-12-25 11:12 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 [this message]
2021-12-25 16:27       ` Soft Works
2021-12-25 16:23     ` Soft Works
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=20211225111202.GT2829255@pb2 \
    --to=michael@niedermayer.cc \
    --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