From: Dave Love <fx@gnu.org>
To: 25139@debbugs.gnu.org
Subject: bug#25139: making the update procedure more obvious
Date: Thu, 08 Dec 2016 15:28:11 +0000 [thread overview]
Message-ID: <874m2e7850.fsf@pc102091.liv.ac.uk> (raw)
It's not very obvious to a newcomer how to update to a new release as
it's rather buried in the doc. I think it would help to reference
"pull" in the installation section of the manual, and maybe in release
announcements, and to index "upgrading" and/or "upgrades" in the manual.
I'm not sure it's worth me suggesting a patch, but I could if it helps.
next reply other threads:[~2016-12-08 15:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 15:28 Dave Love [this message]
2016-12-19 14:09 ` bug#25139: making the update procedure more obvious Ludovic Courtès
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=874m2e7850.fsf@pc102091.liv.ac.uk \
--to=fx@gnu.org \
--cc=25139@debbugs.gnu.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).