From: "softworkz ." <softworkz@hotmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [POLL] [VOTE] code.ffmpeg.org
Date: Wed, 16 Jul 2025 05:46:00 +0000
Message-ID: <BN0P223MB03580D255CFDE2C082BEAC00BA56A@BN0P223MB0358.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <4b23cd1-b710-2e36-dc92-1c4767229758@martin.st>
> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> Martin Storsjö
> Sent: Dienstag, 15. Juli 2025 20:09
> To: FFmpeg development discussions and patches <ffmpeg-
> devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [POLL] [VOTE] code.ffmpeg.org
>
[..]
> like a reasonable way to me. But the end goal should be one canonical
> tool/process, not many in parallel IMO.
+1
I'd rather stick to the ML - no matter how much I dislike it - than having
split communication and needing to visit and work at two places.
For a test/transition phase it's fine of course.
Best regards,
sw
_______________________________________________
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-16 5:46 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-13 11:43 Michael Niedermayer
2025-07-13 11:49 ` Kieran Kunhya via ffmpeg-devel
2025-07-13 11:58 ` Timo Rothenpieler
2025-07-13 15:57 ` Michael Niedermayer
2025-07-13 16:07 ` Timo Rothenpieler
2025-07-13 16:15 ` Timo Rothenpieler
2025-07-13 18:51 ` Kieran Kunhya via ffmpeg-devel
2025-07-13 19:03 ` Yalda
2025-07-13 14:38 ` Rémi Denis-Courmont
2025-07-13 15:56 ` Jacob Lifshay
2025-07-13 15:58 ` Timo Rothenpieler
2025-07-13 17:35 ` Michael Niedermayer
2025-07-13 18:04 ` Ronald S. Bultje
2025-07-13 19:47 ` Timo Rothenpieler
2025-07-13 21:47 ` Michael Niedermayer
2025-07-13 22:07 ` Kieran Kunhya via ffmpeg-devel
2025-07-13 21:55 ` Philip Langdale via ffmpeg-devel
2025-07-13 22:04 ` Timo Rothenpieler
2025-07-13 22:22 ` Marvin Scholz
2025-07-14 2:43 ` Zhao Zhili
2025-07-14 5:50 ` Steven Liu
2025-07-14 9:40 ` Hendrik Leppkes
2025-07-14 9:54 ` Lynne
2025-07-14 9:57 ` Gyan Doshi
2025-07-14 21:29 ` Alexander Strasser via ffmpeg-devel
2025-07-14 23:51 ` softworkz .
2025-07-15 12:48 ` Leo Izen
2025-07-15 18:09 ` Martin Storsjö
2025-07-15 18:24 ` Frank Plowman
2025-07-16 5:46 ` softworkz . [this message]
2025-07-16 10:28 ` Kacper Michajlow
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=BN0P223MB03580D255CFDE2C082BEAC00BA56A@BN0P223MB0358.NAMP223.PROD.OUTLOOK.COM \
--to=softworkz@hotmail.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