From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] Notifications for the new monolithic tool
Date: Wed, 23 Jul 2025 17:50:06 -0300
Message-ID: <2dd4019f-feaf-4f40-9ff4-a63d46f76da0@gmail.com> (raw)
In-Reply-To: <aIE24Z6-ZBiXNda5@phare.normalesup.org>
[-- Attachment #1.1.1: Type: text/plain, Size: 666 bytes --]
On 7/23/2025 4: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.
>
> Thanks.
If you register an account you'll get emails about new PRs if you're a
maintainer (Poke Timo to set you up). But i agree the mailing list
should get such emails during this testing period at least.
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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-23 20:50 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 [this message]
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
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=2dd4019f-feaf-4f40-9ff4-a63d46f76da0@gmail.com \
--to=jamrial@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