From: ludo@gnu.org (Ludovic Courtès)
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: new GuixSD version?
Date: Thu, 21 Jul 2016 14:00:39 +0200 [thread overview]
Message-ID: <871t2nqjyw.fsf@gnu.org> (raw)
In-Reply-To: <CAEwRq=qz5ZLMoSDPdRa84JGHRkkJk_Kp0a1S=o1kSNtBF=jQZw@mail.gmail.com> (Vincent Legoll's message of "Thu, 21 Jul 2016 13:44:31 +0200")
Vincent Legoll <vincent.legoll@gmail.com> skribis:
>> Please report the confusing error messages. We need to improve them,
>> but we need to know exactly what you see and what’s confusing about it!
>> Old farts like are too much brain-damaged to even realize that error
^^
Like me!
>> messages are confusing. ;-)
>
> OK I'll retry and report the error message here.
Thanks!
Ludo’.
next prev parent reply other threads:[~2016-07-21 12:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 21:36 new GuixSD version? Ethan Stefan Day
2016-07-20 3:55 ` Leo Famulari
2016-07-20 4:45 ` Ethan Stefan Day
2016-07-20 5:59 ` Leo Famulari
2016-07-20 13:34 ` Ludovic Courtès
2016-07-20 14:13 ` Vincent Legoll
2016-07-21 11:35 ` Ludovic Courtès
2016-07-21 11:44 ` Vincent Legoll
2016-07-21 12:00 ` Ludovic Courtès [this message]
2016-07-21 19:23 ` Ethan Stefan Day
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=871t2nqjyw.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=help-guix@gnu.org \
--cc=vincent.legoll@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.
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).