From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Julien Lepiller <julien@lepiller.eu>
Cc: 35913@debbugs.gnu.org
Subject: bug#35913: [core-updates] Building "doc/guix.de.texi" fails
Date: Thu, 6 Jun 2019 10:22:16 +0200 [thread overview]
Message-ID: <20190606082216.lusruq2ylcty52ho@pelzflorian.de> (raw)
In-Reply-To: <8695FEB0-01BE-4668-A3DD-74D964CA17C1@lepiller.eu>
On Thu, Jun 06, 2019 at 10:09:23AM +0200, Julien Lepiller wrote:
> Isn't there a comma in a node name? There shouldn't be any, it makes texinfo confused.
>
>
>
Sorry! Please remove the comma from “Preparing to Use the Bootstrap
Binaries”’ translation.
next prev parent reply other threads:[~2019-06-06 8:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-26 6:50 bug#35913: [core-updates] Building "doc/guix.de.texi" fails Marius Bakke
2019-06-06 7:50 ` Ludovic Courtès
2019-06-06 8:09 ` Julien Lepiller
2019-06-06 8:22 ` pelzflorian (Florian Pelz) [this message]
2020-04-07 19:35 ` bug#35913: Marius Bakke
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=20190606082216.lusruq2ylcty52ho@pelzflorian.de \
--to=pelzflorian@pelzflorian.de \
--cc=35913@debbugs.gnu.org \
--cc=julien@lepiller.eu \
/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).