Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Paul B Mahol <onemda@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] trac backups
Date: Wed, 13 Sep 2023 11:52:58 +0200
Message-ID: <CAPYw7P6dx9HZOb8MBvmgKLxvH4xWPu4Z-6qwCd_H5z4aCq_0Bw@mail.gmail.com> (raw)
In-Reply-To: <400dd26f-ee8f-4bea-92ac-5efcaeb77a37@betaapp.fastmail.com>

On Wed, Sep 13, 2023 at 11:05 AM Jean-Baptiste Kempf <jb@videolan.org>
wrote:

> On Wed, 13 Sep 2023, at 01:33, Michael Niedermayer wrote:
> >> Who else other than you has access to the infrastructure?
> >
> > all the root admins do
> > but that isnt the problem, even if 100 more people had access
> > the only way that was noticable it seems was if someone looked
>
> I disagree. The infrastructure is un-documented, and the people accessing
> it are un-documented.
>
> This is a big problem.
>

+1


>
> jb
> --
> Jean-Baptiste Kempf -  President
> +33 672 704 734
> _______________________________________________
> 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".
>
_______________________________________________
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-09-13  9:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-12 22:13 Michael Niedermayer
2023-09-12 22:32 ` Marvin Scholz
2023-09-12 23:33   ` Michael Niedermayer
2023-09-13  9:05     ` Jean-Baptiste Kempf
2023-09-13  9:52       ` Paul B Mahol [this message]
2023-09-13 16:38       ` 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=CAPYw7P6dx9HZOb8MBvmgKLxvH4xWPu4Z-6qwCd_H5z4aCq_0Bw@mail.gmail.com \
    --to=onemda@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