From: Lars Ingebrigtsen <larsi@gnus.org>
To: Bob Newell <bobnewell@bobnewell.net>
Cc: ding@gnus.org
Subject: Re: Space in Gcc name taken as list?
Date: Sun, 14 Nov 2021 02:22:19 +0100 [thread overview]
Message-ID: <87sfvzfs50.fsf@gnus.org> (raw)
In-Reply-To: <87czn4j8s4.fsf@emailmessageidheader.nil> (Bob Newell's message of "Sat, 13 Nov 2021 06:54:35 -1000")
Bob Newell <bobnewell@bobnewell.net> writes:
> I experimentally changed " ,\n\t" to ",\n\t" and " ," to ","
> and everything works as expected. This might be a candidate
> for a patch to the master branch if Eric and Lars agree.
I've now adjusted the two as you suggest on master.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2021-11-14 1:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-13 3:23 Bob Newell
2021-11-13 9:31 ` Robert Pluim
2021-11-13 16:54 ` Bob Newell
2021-11-14 1:22 ` Lars Ingebrigtsen [this message]
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=87sfvzfs50.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=bobnewell@bobnewell.net \
--cc=ding@gnus.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 NNTP newsgroup(s).