From: Timo Rothenpieler <timo@rothenpieler.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] Notifications for the new monolithic tool
Date: Thu, 24 Jul 2025 14:08:58 +0200
Message-ID: <ed643221-1170-4dc5-8a2a-8a70facb8bdc@rothenpieler.org> (raw)
In-Reply-To: <9fe76bed-32d9-432e-be0a-be00a2a513c7@lynne.ee>
On 24/07/2025 03:55, Lynne wrote:
> On 24/07/2025 07:06, Timo Rothenpieler wrote:
>> On 7/23/2025 9:24 PM, Nicolas George wrote:
>>> Hi. I just saw somebody mention this on trac:
>>>
>>> https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20025
>>>
>>> But I have no trace of it in my inbox. If this is now an accepted way of
>>> getting contributions, then either the devel mailing-list should receive
>>> notifications or it should be made very clear here, repeatedly, that
>>> people need to subscribe to some other kind of notifications.
>> I've registered a dummy-user with the ffmpeg-devel address as its E-
>> Mail and subscribed it to all the repo notifications.
>>
>> So things will get forwared to the ML via it now.
>>
>> Hope that's not too spammy, but it should generally only be issues,
>> issue comments and PRs and comments.
>
> That's way too spammy. Those wishing to stay on the ML should respect
> the decision of the vote and make an account.
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 do see the issue that splitting the existing developer base off though.
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.
_______________________________________________
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:[~2025-07-24 12:08 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 [this message]
2025-07-24 15:09 ` Nicolas George
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=ed643221-1170-4dc5-8a2a-8a70facb8bdc@rothenpieler.org \
--to=timo@rothenpieler.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