From: Hartmut Goebel <hartmut@goebel-consult.de>
To: help-guix@gnu.org
Subject: Re: downloading a tarball
Date: Fri, 24 Mar 2017 15:33:14 +0100 [thread overview]
Message-ID: <58D52E2A.3040203@goebel-consult.de> (raw)
In-Reply-To: <70f61b82-be0d-e493-6841-cb2d121f3051@tobias.gr>
Am 24.03.2017 um 14:14 schrieb Tobias Geerinckx-Rice:
>> > HTH - speaking from experience making the same mistake here..
> I suspect most people have. The message isn't as clear as it could be.
Either way round the message is hard to read: squezzed between many
other message, no line-break and arguable wording. IMHO this should be
improved to empower more people.
--
+++hartmut
| Hartmut Goebel | |
| hartmut@goebel-consult.de | www.goebel-consult.de |
next prev parent reply other threads:[~2017-03-24 14:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 12:06 downloading a tarball Catonano
2017-03-24 12:26 ` Ben Woodcroft
2017-03-24 13:14 ` Tobias Geerinckx-Rice
2017-03-24 14:33 ` Hartmut Goebel [this message]
2017-03-24 22:10 ` Ludovic Courtès
2017-03-25 16:43 ` Hartmut Goebel
2017-03-25 8:47 ` Catonano
2017-03-25 10:30 ` Ben Woodcroft
2017-03-24 12:50 ` Ricardo Wurmus
2017-03-24 13:16 ` Catonano
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=58D52E2A.3040203@goebel-consult.de \
--to=hartmut@goebel-consult.de \
--cc=help-guix@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.
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).