From: Jonathan Corbet <corbet@lwn.net>
To: Manuel Ebner <manuelebnerli@mailbox.org>,
Manuel Ebner <manuelebnerli@mailbox.org>,
Shuah Khan <skhan@linuxfoundation.org>,
workflows@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ver_linux: add comparison with required version and colour to output
Date: Fri, 14 Aug 2026 08:01:41 -0600 [thread overview]
Message-ID: <871pc0g5ru.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260814134931.2281085-2-manuelebnerli@mailbox.org>
Manuel Ebner <manuelebnerli@mailbox.org> writes:
> Add the required version from changes.rst.
> Add code for comparison and print in colour (blue, green, red) depending
> on the result of the comparison.
>
> Signed-off-by: Manuel Ebner <manuelebnerli@mailbox.org>
> ---
> I had this patch on my mind for more than half a year. I was convinced I
> couldn't do it because awk is such a special language. Took me less than
> an hour without AI - WTF
>
> Somehow I messed up the formating of the output. I guess it's this lines
> + ofmt = "%-20s\t%s\n"
> but I couldn't figure it out :(
> ---
> scripts/ver_linux | 109 +++++++++++++++++++++++++---------------------
> 1 file changed, 60 insertions(+), 49 deletions(-)
Honestly, I don't think this is going to go very far.
- You don't know that the output of the script is a terminal accepting
ANSI escapes.
- You don't know if the user is running in light or dark mode
- Color blindness must be taken into account
If you really want to add this feature, you need to make it selectable
and configurable. I honestly don't see that it would be worth it.
Thanks,
jon
prev parent reply other threads:[~2026-08-14 14:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 13:49 [PATCH] ver_linux: add comparison with required version and colour to output Manuel Ebner
2026-08-14 14:00 ` Geert Uytterhoeven
2026-08-14 14:01 ` 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=871pc0g5ru.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=manuelebnerli@mailbox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.