unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "(" <paren@disroot.org>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
	mail@cbaines.net, 59313@debbugs.gnu.org
Subject: [bug#59313] [PATCH] gnu: linux-libre: Enable building html and info doc.
Date: Tue, 22 Nov 2022 05:32:26 -0500	[thread overview]
Message-ID: <87zgcjnuth.fsf@gmail.com> (raw)
In-Reply-To: <COIMHH98YOX3.174VUADP2K321@guix-framework> (paren@disroot.org's message of "Tue, 22 Nov 2022 06:49:22 +0000")

Hi,

"(" <paren@disroot.org> writes:

> On Tue Nov 22, 2022 at 6:46 AM GMT, Ludovic Courtès wrote:
>> Nitpick: I’d write “[arguments]” rather than “[phases]”.
>
> ``[arguments]<#:phases>'' would be better, no?

To nitpick myself, if we want to stick to the canonical GNU ChangeLog
style (in its most modern revision), we wouldn't use square brackets as
that is meant for conditional changes [0, 1]; we'd only use ( ) for the
variable name then < > to denote where the change occurred.

Unfortunately < > are a pain to use (breaks auto-completion for some
reason).

[0] info '(standards) Conditional Changes'
[1] info '(standards) Indicating the Part Changed'

-- 
Thanks,
Maxim




  reply	other threads:[~2022-11-22 10:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-16 16:55 [bug#59313] [PATCH] gnu: linux-libre: Enable building html and info doc Maxim Cournoyer
2022-11-20 11:31 ` Christopher Baines
2022-11-21  0:57   ` Maxim Cournoyer
2022-11-21  1:03   ` [bug#59313] [PATCH v2] " Maxim Cournoyer
2022-11-22  6:46     ` [bug#59313] [PATCH] " Ludovic Courtès
2022-11-22  6:49       ` ( via Guix-patches via
2022-11-22 10:32         ` Maxim Cournoyer [this message]
2022-11-24 21:37       ` bug#59313: " Maxim Cournoyer

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=87zgcjnuth.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=59313@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=mail@cbaines.net \
    --cc=paren@disroot.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).