From: Chris Marusich <cmmarusich@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: GNU ChangeLog Format: <> or []?
Date: Thu, 13 Jun 2019 20:48:26 -0700 [thread overview]
Message-ID: <87d0jg3jzp.fsf@gmail.com> (raw)
In-Reply-To: <87k1dp7v71.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Thu, 13 Jun 2019 10:23:44 +0200")
[-- Attachment #1: Type: text/plain, Size: 1237 bytes --]
Hi Ludo,
Ludovic Courtès <ludo@gnu.org> writes:
> Chris Marusich <cmmarusich@gmail.com> skribis:
>
>> Ludovic Courtès <ludo@gnu.org> writes:
>>
>>> Square brackets are used for conditionals, but I also use them for
>>> nested entities. I’m pretty sure I didn’t make it up, but I don’t know
>>> where I took it from!
>>
>> I didn't realize that. It makes sense, though! Is using it for nested
>> entities a common GNU ChangeLog idiom?
>
> It is in Guile and Guix, but that doesn’t count. ;-)
>
> We’d need to look for projects not written in C where there’s actual
> nesting (GNU C nested functions are rarely used, except in glibc.)
I see. That's fair, since Guile and Guix are not the entire world.
>> If so, I wonder if it's worth adding it to the GNU Standards document.
>
> Maybe, though be aware that attempting to change the Standards can be
> time-consuming and frustrating…
I can imagine. Maybe it isn't worth expending the effort for something
that seems so trivial, especially since as you mentioned we would need
to be able to point to a lot of projects and say, "They do it, too."
I'm content just knowing how it's used in Guile and Guix! Thank you.
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2019-06-14 3:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 4:14 GNU ChangeLog Format: <> or []? Chris Marusich
2019-06-10 9:43 ` Ludovic Courtès
2019-06-13 4:34 ` Chris Marusich
2019-06-13 8:23 ` Ludovic Courtès
2019-06-14 3:48 ` Chris Marusich [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d0jg3jzp.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).