From: Carlos O'Donell <carlos@redhat.com>
To: Florian Weimer <fweimer@redhat.com>,
"Dmitry V. Levin" <ldv@altlinux.org>,
Andreas Schwab <schwab@suse.de>
Cc: libc-alpha@sourceware.org
Subject: Re: One test per line, one source per line, etc. etc. etc.
Date: Mon, 28 Jun 2021 07:45:52 -0400 [thread overview]
Message-ID: <d7f241d3-cfca-d29f-96c8-e6a1e75dbedb@redhat.com> (raw)
In-Reply-To: <87y2auuwx5.fsf@oldenburg.str.redhat.com>
On 6/28/21 6:05 AM, Florian Weimer via Libc-alpha wrote:
> routines += \
> read \
> write \
> # routines
Floian, Dmitry,
This is my *favourite* because it increases observability
of the list you're editing. Thanks for exploring the options.
Andreas,
Any objection to the above? As Florian noted it works and
subsequent variable setting after "# routines" works as
expected.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2021-06-28 11:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-27 19:58 Carlos O'Donell
2021-06-27 20:14 ` Florian Weimer
2021-06-27 21:52 ` Carlos O'Donell
2021-06-28 7:24 ` Andreas Schwab
2021-06-28 11:42 ` Carlos O'Donell
2021-06-28 9:22 ` Dmitry V. Levin
2021-06-28 10:05 ` Florian Weimer
2021-06-28 11:45 ` Carlos O'Donell [this message]
2021-06-28 18:52 ` DJ Delorie
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=d7f241d3-cfca-d29f-96c8-e6a1e75dbedb@redhat.com \
--to=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=ldv@altlinux.org \
--cc=libc-alpha@sourceware.org \
--cc=schwab@suse.de \
/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).