From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] MAINTAINERS: add a separate list for those with push access
Date: Tue, 7 Feb 2023 02:27:53 +0100
Message-ID: <20230207012753.GR1949656@pb2> (raw)
In-Reply-To: <d3200f56-f349-754c-31d3-13aa3c858d63@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1101 bytes --]
On Mon, Feb 06, 2023 at 02:49:19PM +0000, Derek Buitenhuis wrote:
> On 2/6/2023 12:10 PM, Lynne wrote:
> > At the FOSDEM meeting yesterday, everyone there agreed that while it's not
> > perfect, it's a step in the right direction, and we should merge this.
>
> (I have no opinion re: merging.)
>
> Is it not possible to audit/list who has git push access instead of guessing?
I will send you (and any other developer who wants) the list of git user names
who have write access
I am slightly hesitant to post this list publically as its not really what
people want and posting any username lists may have other "uses"
Also there are people in this list who have not been active in ffmpeg git
and iam not sure if they agree to be listed publically
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
If the United States is serious about tackling the national security threats
related to an insecure 5G network, it needs to rethink the extent to which it
values corporate profits and government espionage over security.-Bruce Schneier
[-- 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".
next prev parent reply other threads:[~2023-02-07 1:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 1:13 Lynne
2022-12-15 19:34 ` Michael Niedermayer
2022-12-15 23:26 ` Lynne
2022-12-16 22:05 ` Michael Niedermayer
2022-12-18 6:31 ` Lynne
2023-01-29 23:14 ` Lynne
2023-01-30 3:44 ` Leo Izen
2023-01-30 3:59 ` Gyan Doshi
2023-01-30 4:22 ` Stephen Hutchinson
2023-02-07 2:40 ` Steven Liu
2023-01-30 16:49 ` Michael Niedermayer
2023-01-30 19:03 ` Lynne
2023-02-06 12:10 ` Lynne
2023-02-06 14:49 ` Derek Buitenhuis
2023-02-07 1:27 ` Michael Niedermayer [this message]
2023-02-07 1:20 ` Michael Niedermayer
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=20230207012753.GR1949656@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