unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: "Timothy Sample" <samplet@ngyro.com>,
	"Ludovic Courtès" <ludo@gnu.org>,
	"Nicolas Goaziou" <mail@nicolasgoaziou.fr>,
	39655@debbugs.gnu.org
Subject: [bug#39655] [PATCH core-updates] doc: Add 'Scheme-only Bootstrap' node.
Date: Mon, 18 May 2020 09:57:45 +0300	[thread overview]
Message-ID: <20200518065745.GD18220@E5400> (raw)
In-Reply-To: <87k119rewo.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 2571 bytes --]

On Mon, May 18, 2020 at 07:27:35AM +0200, Jan Nieuwenhuizen wrote:
> Nicolas Goaziou writes:
> 
> Hello Nicolas,
> 
> >> Jan Nieuwenhuizen writes:
> >
> > I have some Texinfo syntax nitpicks, if you do not mind.
> 
> Nitpicks are great.
> 
> >> +re-create them if needed (see @pxref{Preparing to Use the Bootstrap
> >> +Binaries}).
> >
> > Please remove the "see", included in @pxref.
> 
> Right.
> 
> >> +Building the GNU System from source is currently only possibly by adding
> >> +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
> >
> > Suggestion: "and some others.  For details, see ..."
> 
> Better.
> 
> >> +@file{gnu/packages/commencement.scm}}.  As Gash and Gash Utils mature,
> >
> > Missing full stop at the end of the footnote.
> 
> Added.
> 
> >> +and GNU packages become more bootstrappable again (e.g., new releases of
> >> +GNU Sed will also ship in @code{tar.gz} format), this set of added
> >> +packages can hopefully be reduced again.
> >
> > @code{tar.gz} seems odd there.
> >
> > Suggestion: @file{.tar.gz} if this is about the suggestion, or
> > ``tar.gz'', or "as compressed tar files".
> >
> > If none is satisfying, @samp{tar.gz} is still better than @code{tar.gz},
> > IMO.
> 
> Ah, and now I see that it's too cryptic/terse too.  How about
> 
> and GNU packages become more bootstrappable again (e.g., new releases of
> GNU Sed will also ship as gzipped tarballs again, as alternative to the
> non-bootstrappable @code{xz}-compression), this set of added packages
> can hopefully be reduced again.

I have to ask since we're talking about bootstrapability; is it actually
not bootstrappable or is it just harder/more complex? (The question is
more about the wording than about the logistics of it.)

> 
> >> +If you are interested, join us on @code{#bootstrappable} on the
> >> Freenode
> >
> > Arguably, I would use @samp, not @code.
> 
> Good.
> 
> >> +IRC network or discuss on @code{bug-mes@@gnu.org} or
> >
> > @code -> @email
> >
> >> +@code{gash-devel@@nongnu.org}.
> >
> > Ditto.
> 
> Sure, 2x.
> 
> Updated version attached.  Thank you!  
> 
> Greetings,
> Janneke
> 



-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-05-18  6:59 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 [this message]
2020-05-18  7:37             ` Jan Nieuwenhuizen
2020-05-18  7:37           ` Nicolas Goaziou
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=20200518065745.GD18220@E5400 \
    --to=efraim@flashner.co.il \
    --cc=39655@debbugs.gnu.org \
    --cc=janneke@gnu.org \
    --cc=ludo@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    --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).