From: Carlos O'Donell <carlos@redhat.com>
To: Andreas Schwab <schwab@linux-m68k.org>,
Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>
Cc: Florian Weimer <fweimer@redhat.com>
Subject: Re: One test per line, one source per line, etc. etc. etc.
Date: Mon, 28 Jun 2021 07:42:55 -0400 [thread overview]
Message-ID: <0bb2b537-e3bf-cda9-e446-bfd39494e5a2@redhat.com> (raw)
In-Reply-To: <87zgva8n9z.fsf@igel.home>
On 6/28/21 3:24 AM, Andreas Schwab wrote:
> On Jun 27 2021, Carlos O'Donell via Libc-alpha wrote:
>
>>> This:
>>>
>>> routines += \
>>> read \
>>> write \
>>
>> This. To reduce conflicts.
>
> The trailing backslash will gobble the next line which is bad.
If you feel there is risk in that, then I'm happy to avoid the
trialing slash since we would still gain from the reduced probability
of conflict with named functions and tests.
Would you be OK if we proceed without the trailing slash?
--
Cheers,
Carlos.
next prev parent reply other threads:[~2021-06-28 11:42 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 [this message]
2021-06-28 9:22 ` Dmitry V. Levin
2021-06-28 10:05 ` Florian Weimer
2021-06-28 11:45 ` Carlos O'Donell
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=0bb2b537-e3bf-cda9-e446-bfd39494e5a2@redhat.com \
--to=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=schwab@linux-m68k.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).