From: Chris Marusich <cmmarusich@gmail.com>
To: guix-devel@gnu.org
Subject: [PATCH 1/2] doc: Clarify that 'guix pull' can't be easily rolled back.
Date: Sun, 29 Jan 2017 20:40:34 -0800 [thread overview]
Message-ID: <20170130044035.22741-2-cmmarusich@gmail.com> (raw)
In-Reply-To: <20170130044035.22741-1-cmmarusich@gmail.com>
* doc/guix.texi (Invoking guix pull): Clarify that 'guix pull' can't be
easily rolled back.
---
doc/guix.texi | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/doc/guix.texi b/doc/guix.texi
index 4ba101094..2a9b11969 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -2337,7 +2337,9 @@ instance, when user @code{root} runs @command{guix pull}, this has no
effect on the version of Guix that user @code{alice} sees, and vice
versa@footnote{Under the hood, @command{guix pull} updates the
@file{~/.config/guix/latest} symbolic link to point to the latest Guix,
-and the @command{guix} command loads code from there.}.
+and the @command{guix} command loads code from there. Currently, the
+only way to roll back an invocation of @command{guix pull} is to
+manually update this symlink to point to the previous Guix.}.
The @command{guix pull} command is usually invoked with no arguments,
but it supports the following options:
--
2.11.0
next prev parent reply other threads:[~2017-01-30 4:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 4:40 Some small documentation improvements Chris Marusich
2017-01-30 4:40 ` Chris Marusich [this message]
2017-02-01 22:44 ` [PATCH 1/2] doc: Clarify that 'guix pull' can't be easily rolled back Ludovic Courtès
2017-01-30 4:40 ` [PATCH 2/2] doc: Discuss encrypted swap space Chris Marusich
2017-01-30 8:53 ` Hartmut Goebel
2017-02-01 22:46 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170130044035.22741-2-cmmarusich@gmail.com \
--to=cmmarusich@gmail.com \
--cc=guix-devel@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 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.