Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Rémi Denis-Courmont" <remi@remlab.net>
To: ffmpeg-devel@ffmpeg.org
Cc: Cc <cc@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Access to the ARM server
Date: Wed, 26 Mar 2025 13:28:37 +0200
Message-ID: <98BBD443-C06D-42AE-A497-C099E6EA45FD@remlab.net> (raw)
In-Reply-To: <CABGuwE=Y-aYr8aCbVSrmifnH2J2SHNKnXHf8gj_z3r6kYLBTtw@mail.gmail.com>

Hi,

I answered, but the position of the CC is such that there is nothing we can do about NG in general.

Suspension will not achieve anything (and in this particular case, seems a bit heavy-handed), and permanent ban is not something that the CC can do under the current CoC.

Br,

Le 25 mars 2025 11:32:38 GMT+02:00, Kieran Kunhya <kieran618@googlemail.com> a écrit :
>Come on, this is being deliberately facetious, FFmpeg has no legal
>entity that they could give it to.
>The server was given to @Jean-Baptiste Kempf for the purposes of
>FFmpeg development and I host it.
>
>Martin makes extensive use of it for development.
>
>@Cc This is unnecessarily aggressive and I would like to report it.
>
>Kieran
>
>On Tue, Mar 25, 2025 at 8:55 AM Nicolas George <george@nsup.org> wrote:
>>
>> Kieran Kunhya via ffmpeg-devel (HE12025-03-25):
>> > The server belongs to @Jean-Baptiste Kempf <jb@videolan.org>
>>
>> Are you saying that the tweet that says “giving ***us*** a 160-core ARM
>> server” (emphasis mine) is a lie?
>>
>> --
>>   Nicolas George
>
_______________________________________________
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:[~2025-03-26 11:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-25  8:46 Zhao Zhili
2025-03-25  8:52 ` Kieran Kunhya via ffmpeg-devel
2025-03-25  8:55   ` Nicolas George
2025-03-25  9:32     ` Kieran Kunhya via ffmpeg-devel
2025-03-26 11:28       ` Rémi Denis-Courmont [this message]
2025-03-28 13:01       ` Michael Niedermayer
2025-03-26 11:26     ` Rémi Denis-Courmont

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=98BBD443-C06D-42AE-A497-C099E6EA45FD@remlab.net \
    --to=remi@remlab.net \
    --cc=cc@ffmpeg.org \
    --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