From: Jonathan Corbet <corbet@lwn.net>
To: Hans Anda <hansa@airmail.cc>,
Collin Funk <collin.funk1@gmail.com>,
Shuah Khan <skhan@linuxfoundation.org>
Cc: workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, Hans Anda <hansa@airmail.cc>
Subject: Re: [PATCH] scripts: sort ver_linux and list in changes.rst
Date: Mon, 23 Feb 2026 14:56:54 -0700 [thread overview]
Message-ID: <87wm032kex.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260221152113.28322-2-hansa@airmail.cc>
Hans Anda <hansa@airmail.cc> writes:
> It is a pain in the ass to compare the software versions on the running
> system (scripts/ver_linux) with the minimal required versions (changes.rst).
>
> Sort both lists alphabetically
So ... I suspect that the intent, in changes.rst anyway, was to list the
compilers first and group other stuff roughly by category. But I agree
it's kind of a mess; if it's really by category, they should be
explicit.
If nobody screams, I am inclined to apply this change. But ...
> Add missing tools in ver_linux
> (bash, bc, bindgen, bindutils, btrfs, clang, e2fsck, awk, tar, gtags,
> iptables, kmod, mcelog, mkimage, openssl, pahole, python, Rust, sphinx,
> squashfs-tools, udev)
> Fix minor issues (add grub2)
...these are a separate change and should be in their own patch.
Thanks,
jon
prev parent reply other threads:[~2026-02-23 21:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-21 15:21 Hans Anda
2026-02-23 21:56 ` Jonathan Corbet [this message]
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=87wm032kex.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=collin.funk1@gmail.com \
--cc=hansa@airmail.cc \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=workflows@vger.kernel.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox