Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Derek Buitenhuis <derek.buitenhuis@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] MAINTAINERS: add a separate list for those with push access
Date: Mon, 6 Feb 2023 14:49:19 +0000
Message-ID: <d3200f56-f349-754c-31d3-13aa3c858d63@gmail.com> (raw)
In-Reply-To: <NNacXMy--3-9@lynne.ee>

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?

This kind of comes back to what we discussed at the December dev meeting - 
we don't even know who has access to our infra... that is insane.

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

  reply	other threads:[~2023-02-06 14:49 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 [this message]
2023-02-07  1:27         ` Michael Niedermayer
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=d3200f56-f349-754c-31d3-13aa3c858d63@gmail.com \
    --to=derek.buitenhuis@gmail.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