From: Alejandro Colomar <alx@kernel.org>
To: libc-alpha@sourceware.org
Cc: Alejandro Colomar <alx@kernel.org>,
Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
Subject: [PATCH v1b 0/3] Makeconfig: reflow and other whitespace changes
Date: Mon, 17 Jul 2023 22:02:17 +0200 [thread overview]
Message-ID: <20230717200220.569481-1-alx@kernel.org> (raw)
This is a spin-off from the patch set in [1], as suggested by Adhemerval.
I used v1b, to mark that it's v1 of the spin-off.
This patch set depends on [2].
[1]: <https://inbox.sourceware.org/libc-alpha/24a77842-d991-6357-7c88-143b113a22df@linaro.org/T/#m0f23a066331ffd792374b4d3e2830440f9caeab2>
[2]: <https://inbox.sourceware.org/libc-alpha/20230711205652.46362-1-alx@kernel.org/T/#u>
Disclaimer: I only tested it lightly: configure + make.
Alejandro Colomar (3):
Makeconfig: Use a space before a newline escape
Makeconfig: Use one line per token
Makeconfig: Use spaces consistently before =
Makeconfig | 643 ++++++++++++++++++++++++++++++++++++++---------------
1 file changed, 469 insertions(+), 174 deletions(-)
Range-diff (compared to [1]):
1: 55d7caa944 < -: ---------- Makeconfig: Use one line per token
2: efb21da36c < -: ---------- Makeconfig: Compile glibc with -fno-delete-null-pointer-checks
-: ---------- > 1: dd70347aaa Makeconfig: Use a space before a newline escape
-: ---------- > 2: eb0ccc5b82 Makeconfig: Use one line per token
-: ---------- > 3: 3dde03c104 Makeconfig: Use spaces consistently before =
--
2.40.1
next reply other threads:[~2023-07-17 20:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 20:02 Alejandro Colomar [this message]
2023-07-17 20:02 ` [PATCH v1b 1/3] Makeconfig: Use a space before a newline escape Alejandro Colomar
2023-07-17 20:02 ` [PATCH v1b 2/3] Makeconfig: Use one line per token Alejandro Colomar
2023-07-17 20:02 ` [PATCH v1b 3/3] Makeconfig: Use spaces consistently before = Alejandro Colomar
2023-07-17 20:04 ` [PATCH v1b 0/3] Makeconfig: reflow and other whitespace changes Alejandro Colomar
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=20230717200220.569481-1-alx@kernel.org \
--to=alx@kernel.org \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).