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>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [PATCH v2] ver_linux: add comparison with required version and add rows and colour to output
Date: Fri, 14 Aug 2026 12:46:26 -0600 [thread overview]
Message-ID: <87o6f4ee0t.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260814143212.2288631-2-manuelebnerli@mailbox.org>
Manuel Ebner <manuelebnerli@mailbox.org> writes:
> Add the required version from changes.rst.
> Add code for comparison and print '###' in the respective row (good, bad) and in
> the respective colour (blue, green, red) depending on the result of the comparison.
>
> Signed-off-by: Manuel Ebner <manuelebnerli@mailbox.org>
> ---
> [v2]
> add colour reset as Geert suggested
> change output to take colourblindness into account
So that suggests you read my previous comments, but didn't see fit to
look at all of them or respond.
*How* are you taking colorblindness into account? Which type of
colorblindness have you tried to address. Certainly not red/green
which, I believe, is the most common form.
But, more to the point:
- You do not know that your output is going to a terminal at all, much
less one that understands these escape sequences.
- You do not know whether that terminal, if it exists, is in dark mode
or not.
- You don't check NO_COLOR to see whether the user has explicitly asked
to not have colorized output.
This is a simple script meant to check dependencies, it really does not
need this kind of silliness. Surely there is something more useful you
could work on?
jon
prev parent reply other threads:[~2026-08-14 18:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 14:32 Manuel Ebner
2026-08-14 18:16 ` Randy Dunlap
2026-08-14 18:46 ` 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=87o6f4ee0t.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=geert@linux-m68k.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®