public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@redhat.com>
To: libc-alpha@sourceware.org
Cc: Carlos O'Donell <carlos@redhat.com>
Subject: [PATCH 0/2] Standardize the sorting of Makefile variables
Date: Fri, 28 Apr 2023 07:48:09 -0400	[thread overview]
Message-ID: <20230428114811.4129539-1-carlos@redhat.com> (raw)

The project has started to re-flow and sort Makefile variables to make
it easier to manage the lists of inputs and tests.  While splitting the
lines is easy to do, the sorting is more onerous because of the desire
to sort like tests with like tests.  The following is my attempt to
standardize teh sorting following the consensus discussion on the list
which suggested using LC_COLLATE=C and sorting similar tests in
numerical order of their prefix.

The series re-flows and then sorts sysdeps/pthread/Makefile using the
new helper python script.

Carlos O'Donell (2):
  nptl: Re-flow and sort variables in Makefile.
  scripts: Add sort-makefile-lines.py to sort Makefile variables.

 scripts/sort-makefile-lines.py                | 217 +++++++++
 sysdeps/pthread/Makefile                      | 433 +++++++++++++-----
 .../{tst-mutex7robust.c => tst-robust11.c}    |   0
 3 files changed, 537 insertions(+), 113 deletions(-)
 create mode 100755 scripts/sort-makefile-lines.py
 rename sysdeps/pthread/{tst-mutex7robust.c => tst-robust11.c} (100%)

-- 
2.39.2


             reply	other threads:[~2023-04-28 11:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-28 11:48 Carlos O'Donell [this message]
2023-04-28 11:48 ` [PATCH 1/2] nptl: Re-flow and sort variables in Makefile Carlos O'Donell
2023-05-08 17:17   ` Siddhesh Poyarekar
2023-05-08 17:53     ` Siddhesh Poyarekar
2023-04-28 11:48 ` [PATCH 2/2] scripts: Add sort-makefile-lines.py to sort Makefile variables Carlos O'Donell
2023-05-08 17:47   ` Siddhesh Poyarekar
2023-05-09 17:58     ` Carlos O'Donell

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=20230428114811.4129539-1-carlos@redhat.com \
    --to=carlos@redhat.com \
    --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).