unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: "Timothy Sample" <samplet@ngyro.com>,
	"Ludovic Courtès" <ludo@gnu.org>,
	39655@debbugs.gnu.org
Subject: [bug#39655] [PATCH core-updates] doc: Add 'Scheme-only Bootstrap' node.
Date: Mon, 18 May 2020 09:37:34 +0200	[thread overview]
Message-ID: <87k119sngh.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87k119rewo.fsf@gnu.org> (Jan Nieuwenhuizen's message of "Mon, 18 May 2020 07:27:35 +0200")

Hello,

I have a couple more nits.

Jan Nieuwenhuizen <janneke@gnu.org> writes:

> +Taking the bootstrap binaries for granted means that we consider them to
> +be a correct and trustworthy `seed' for building the complete system.

OOC, why are you using single quotes here? You used double quotes
everywhere else. I assume this is an omission.

> +some historical GNU packages as intermediate steps@footnote{Packages
> +such as @code{gcc-2.95.3}, @code{binutils-2.14}, @code{glibc-2.2.5},
> +@code{gzip-1.2.4}, @code{tar-1.22}, and some others.  for details,
> see

"for" -> "For"


Regards,

-- 
Nicolas Goaziou




  parent reply	other threads:[~2020-05-18  7:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-18 12:44 [bug#39655] [PATCH core-updates] doc: Add 'Scheme-only Bootstrap' node Jan Nieuwenhuizen
2020-02-19 15:58 ` Ludovic Courtès
2020-05-17 12:43   ` Jan Nieuwenhuizen
2020-05-17 12:51     ` Jan Nieuwenhuizen
2020-05-17 22:05       ` Nicolas Goaziou
2020-05-18  5:27         ` Jan Nieuwenhuizen
2020-05-18  6:57           ` Efraim Flashner
2020-05-18  7:37             ` Jan Nieuwenhuizen
2020-05-18  7:37           ` Nicolas Goaziou [this message]
2020-05-18  7:50             ` Jan Nieuwenhuizen
2020-05-18 17:53     ` Timothy Sample
2020-05-22 14:20       ` bug#39655: " Jan Nieuwenhuizen

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=87k119sngh.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=39655@debbugs.gnu.org \
    --cc=janneke@gnu.org \
    --cc=ludo@gnu.org \
    --cc=samplet@ngyro.com \
    /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).