From: Stefano Sabatini <stefasab@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] lavf/matroskaenc: sort options by name
Date: Wed, 10 Apr 2024 11:07:32 +0200
Message-ID: <ZhZW0w0ZN7+3XOSa@mariano> (raw)
In-Reply-To: <tencent_AE3C909026D3A7FB2AA853195C4F8B92E606@qq.com>
On date Sunday 2024-04-07 16:01:27 +0800, Zhao Zhili wrote:
>
> > On Apr 7, 2024, at 14:16, Anton Khirnov <anton@khirnov.net> wrote:
> >
> > Quoting Andreas Rheinhardt (2024-04-06 13:25:49)
> >> See https://ffmpeg.org/pipermail/ffmpeg-devel/2024-February/320849.html
> >> Additionally I do not agree that sorting options by name is the best
> >> way; it should be sorted by what are (believed to be) the most commonly
> >> used options.
> >
> > +1
>
> https://patchwork.ffmpeg.org/project/ffmpeg/patch/20240106165246.274472-1-stefasab@gmail.com/
>
> I have the same consideration in another patch. Maybe group related
> options together than sort whole options.
This hardly works for the aforementioned reasons, no objective
criteria means that there will be never a consistent way to sort the
options. What happens in practice is that options are added more or
less randomly, which doesn't help readability and discoverability
especially when there are many options.
_______________________________________________
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:[~2024-04-10 9:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-06 11:10 Stefano Sabatini
2024-04-06 11:25 ` Andreas Rheinhardt
2024-04-06 11:33 ` Stefano Sabatini
2024-04-07 6:16 ` Anton Khirnov
2024-04-07 8:01 ` Zhao Zhili
2024-04-10 9:07 ` Stefano Sabatini [this message]
2024-04-11 9:00 ` Paul B Mahol
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=ZhZW0w0ZN7+3XOSa@mariano \
--to=stefasab@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