From: ludo@gnu.org (Ludovic Courtès)
To: myglc2 <myglc2@gmail.com>
Cc: 25852-done@debbugs.gnu.org
Subject: bug#25852: Users not updating their installations of Guix
Date: Wed, 10 May 2017 22:16:42 +0200 [thread overview]
Message-ID: <878tm4sc0l.fsf@gnu.org> (raw)
In-Reply-To: <86vap8yf36.fsf@gmail.com> (myglc2@gmail.com's message of "Wed, 10 May 2017 10:13:49 -0400")
myglc2 <myglc2@gmail.com> skribis:
> How about extending this ...
>
>> + (warning (G_ "Your Guix installation is getting old. Consider
>> +running 'guix pull' followed by '~a' to get up-to-date
>> +packages and security updates.\n")
>
> ... to inform the user how old the installation is?
Good idea. I did that and pushed as
7fd952e05203d975fcb6cdabd2f742ade1b31b66.
Thanks for your feedback!
Ludo’.
next prev parent reply other threads:[~2017-05-10 20:17 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 21:11 bug#25852: Users not updating their installations of Guix Leo Famulari
2017-02-24 5:42 ` Pjotr Prins
2017-03-02 18:16 ` sirgazil
2017-03-04 20:29 ` Tomáš Čech
2017-03-04 22:43 ` Leo Famulari
2017-03-05 7:56 ` Tomáš Čech
2017-03-05 9:25 ` Pjotr Prins
2017-03-05 9:43 ` Tomáš Čech
2017-03-06 14:52 ` Ricardo Wurmus
2017-03-07 6:54 ` Pjotr Prins
2017-03-06 21:12 ` Ludovic Courtès
2017-03-06 21:34 ` Leo Famulari
2017-03-07 6:33 ` Tomáš Čech
2017-03-07 19:51 ` Leo Famulari
2017-03-07 20:58 ` Tomáš Čech
2017-03-07 22:22 ` Leo Famulari
2017-03-08 6:25 ` Tomáš Čech
2017-03-08 8:45 ` Leo Famulari
2017-03-08 9:24 ` Tomáš Čech
2017-03-08 18:15 ` Leo Famulari
2017-03-09 7:38 ` Efraim Flashner
2017-03-09 10:58 ` Ludovic Courtès
2017-03-09 12:42 ` Tomáš Čech
2017-03-09 15:42 ` Ludovic Courtès
2017-03-07 7:32 ` Mark H Weaver
2017-03-07 10:35 ` Ludovic Courtès
2017-03-11 1:48 ` Mark H Weaver
2017-05-10 13:12 ` Ludovic Courtès
2017-05-10 14:13 ` myglc2
2017-05-10 20:16 ` Ludovic Courtès [this message]
2017-05-12 6:06 ` Ricardo Wurmus
2017-05-12 8:29 ` Ludovic Courtès
2017-05-12 17:10 ` myglc2
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=878tm4sc0l.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=25852-done@debbugs.gnu.org \
--cc=myglc2@gmail.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 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.