[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.2601111743490.30566@angie.orcam.me.uk>
Date: Sun, 11 Jan 2026 17:58:53 +0000 (GMT)
From: "Maciej W. Rozycki" <macro@...am.me.uk>
To: Askar Safin <safinaskar@...il.com>
cc: kernel-janitors@...r.kernel.org, linmag7@...il.com,
linux-alpha@...r.kernel.org, linux-kernel@...r.kernel.org,
mattst88@...il.com, patches@...ts.linux.dev, richard.henderson@...aro.org
Subject: Re: [PATCH 1/1] alpha: trivial: remove ^L chars
On Sun, 11 Jan 2026, Askar Safin wrote:
> > As a matter of interest, why would the presence of ^L characters cause
> > any issues? That is just another instance of white space and it has been
>
> I have shell script, which allows me to remove given config (for example,
> CONFIG_NET) from whole Linux source tree. To do this, this script parses
> .c files, Kconfig files and makefiles. So, I want them to be as predictable
> and easy-to-parse as possible.
What prevents your shell script from interpreting ^L as yet another
white-space character? I don't think any limitation of the tool you've
chosen is by itself a good justification to change the work the tool is
used on. Fix your tool or use another instead, i.e. match your tools to
the work and not the other way round.
> P. S. I don't see your emails in my gmail inbox (not even in spam folder).
Correct, GMail rejects e-mail sent from here. It has for a while now.
Maciej
Powered by blists - more mailing lists