Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Nicolas George <george@nsup.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Notifications for the new monolithic tool
Date: Thu, 24 Jul 2025 17:09:11 +0200
Message-ID: <aIJMl4K0pTGQFQYH@phare.normalesup.org> (raw)
In-Reply-To: <ed643221-1170-4dc5-8a2a-8a70facb8bdc@rothenpieler.org>

Timo Rothenpieler (HE12025-07-24):
> If the "was synchronized" notifications could be disabled, it'd be much more
> reasonable I feel.
> But that does not seem to be an option, it's all or nothing.

I am not sure what you mean here.

If a patch is submitted to the monolithic thing, the patch must be
mirrored on the mailing-list.

If a comment on a patch is submitted to the monolithic thing, the
comment must be mirrored on the mailing-list.

I personally do not care, but you probably want to have it mirrored the
other way around too.

And this:

# View it on FFmpeg Forgejo ( https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20031 ) or reply to this email directly.

is not adequate.

> I do see the issue that splitting the existing developer base off though.

That would be a catastrophe.

> So without this, people might get left behind, so it should be left on until
> at least a significant portion of developers have signed up and gotten added
> to the Team.
> 
> I have not received a single request to be added yet.

You have not documented that it was necessary yet.

Regards,

-- 
  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-07-24 15:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-23 19:24 Nicolas George
2025-07-23 20:50 ` James Almer
2025-07-23 22:06 ` Timo Rothenpieler
2025-07-23 23:36   ` Jacob Lifshay
2025-07-24  1:55   ` Lynne
2025-07-24 12:08     ` Timo Rothenpieler
2025-07-24 15:09       ` Nicolas George [this message]
2025-07-24 16:11         ` Timo Rothenpieler
2025-07-24 16:48           ` Nicolas George
2025-07-24 17:42             ` Timo Rothenpieler
2025-07-24 15:03     ` Nicolas George

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=aIJMl4K0pTGQFQYH@phare.normalesup.org \
    --to=george@nsup.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