From: "Ludovic Courtès" <ludo@gnu.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Install doc + templates overhaul
Date: Mon, 21 Jan 2019 14:56:18 +0100 [thread overview]
Message-ID: <87ef96jerh.fsf@gnu.org> (raw)
In-Reply-To: <87zhrw7b94.fsf@ambrevar.xyz> (Pierre Neidhardt's message of "Sat, 19 Jan 2019 19:28:23 +0100")
Hello Pierre,
Pierre Neidhardt <mail@ambrevar.xyz> skribis:
> I've just re-installed Guix from a 0.16 image. My first time in a year,
> and I've had the opportunity to have a fresh look at the installation
> manual. I've taken note of a few confusing points that gave me a hard
> time installing Guix (even the 2nd time :p) so here they are. I'll send
> a patch to address them if you people agree.
Did you try installing with the new installer? Hopefully most of this
documentation becomes secondary when one uses the installer. :-)
Anyway, the changes you propose overall LGTM.
Thanks,
Ludo’.
next prev parent reply other threads:[~2019-01-21 13:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-19 18:28 Install doc + templates overhaul Pierre Neidhardt
2019-01-21 13:56 ` Ludovic Courtès [this message]
2019-01-21 14:04 ` Pierre Neidhardt
2019-01-21 14:05 ` Pierre Neidhardt
2019-01-21 21:08 ` Pierre Neidhardt
2019-01-21 21:13 ` Pierre Neidhardt
2019-01-22 13:20 ` ‘nss-certs’ missing in the installation image Ludovic Courtès
2019-01-22 14:01 ` Pierre Neidhardt
2019-01-23 9:00 ` Giovanni Biscuolo
2019-01-23 9:42 ` Pierre Neidhardt
2019-01-23 10:59 ` Ludovic Courtès
2019-01-23 11:22 ` Pierre Neidhardt
2019-01-23 14:01 ` swedebugia
2019-01-26 10:17 ` Pierre Neidhardt
2019-01-26 20:53 ` Amin Bandali
2019-01-28 22:48 ` Pierre Neidhardt
2019-01-29 8:33 ` Ludovic Courtès
2019-01-29 11:09 ` Pierre Neidhardt
2019-02-08 14:31 ` Pierre Neidhardt
2019-02-08 21:42 ` Ludovic Courtès
2019-02-10 14:22 ` Pierre Neidhardt
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ef96jerh.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mail@ambrevar.xyz \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.