From: Michael Niedermayer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Michael Niedermayer <michael@niedermayer.cc>
Subject: [FFmpeg-devel] Re: New mailing-list archive
Date: Mon, 13 Oct 2025 23:52:43 +0200
Message-ID: <aO10q-Fmy7es8sj-@neo> (raw)
In-Reply-To: <aOzBwHYRUdKekMHJ@phare.normalesup.org>
[-- Attachment #1.1: Type: text/plain, Size: 1396 bytes --]
Hi Nicolas
On Mon, Oct 13, 2025 at 11:09:20AM +0200, Nicolas George via ffmpeg-devel wrote:
> Nicolas George via ffmpeg-devel (HE12025-10-13):
> > Thanks. It sucks a little less than the first impression. But it still
> > sucks. The fact that it defaults to a non-monospace font, for starters,
> > and tries to “pretty print” the mail is terrible for our use.
>
> Also: threading. For example, this thread
> <https://lists.ffmpeg.org/archives/list/ffmpeg-user@ffmpeg.org/thread/Q4TED2ECCNO4LNH2DSUAH4YZYAMF3QX5/>
> that looks like that wit a MUA that supports threading :
>
> [FFmpeg-user] Bruce Gavin : Access Exception 0xC0000005 from Windows.CreateProcess()
> └─>[FFmpeg-user] Gyan Doshi : Re: Access Exception 0xC0000005 from Windows.CreateProcess()
> ├─> Bruce Gavin
> │ └─> Gyan Doshi
> └─> Bruce Gavin
> └─> Tobias Rapp
>
> On the web version, there is a vague indentation to show the threading,
> but nothing as readable as what we used to have.
theres also:
https://lists.ffmpeg.org/lore/ffmpeg-devel/
https://www.mail-archive.com/ffmpeg-devel@ffmpeg.org/
Also if anyone has suggestions for better mail archieve software or better settings
for ours ...
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Avoid a single point of failure, be that a person or equipment.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 163 bytes --]
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
next prev parent reply other threads:[~2025-10-13 22:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 8:32 [FFmpeg-devel] " Nicolas George via ffmpeg-devel
2025-10-13 8:40 ` [FFmpeg-devel] " Diederick C. Niehorster via ffmpeg-devel
2025-10-13 8:47 ` Nicolas George via ffmpeg-devel
2025-10-13 9:09 ` Nicolas George via ffmpeg-devel
2025-10-13 21:52 ` Michael Niedermayer via ffmpeg-devel [this message]
2025-10-16 11:56 ` Nicolas George via ffmpeg-devel
2025-10-16 17:02 ` Michael Niedermayer via ffmpeg-devel
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=aO10q-Fmy7es8sj-@neo \
--to=ffmpeg-devel@ffmpeg.org \
--cc=michael@niedermayer.cc \
/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