From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: 22273@debbugs.gnu.org
Subject: bug#22273: “guix download” fails with “bad-response”
Date: Wed, 06 Jan 2016 17:28:33 +0100 [thread overview]
Message-ID: <87oacyfz9q.fsf@gnu.org> (raw)
In-Reply-To: <87r3hw2blw.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 05 Jan 2016 18:13:31 +0100")
Fixed in Guile with commit 4c7732c.
This was a bit more work than just using ‘read-line’ because we want to
check that the line delimiter is present, like ‘read-line*’ did.
Thanks,
Ludo’.
next parent reply other threads:[~2016-01-06 16:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <idja8oshv99.fsf@bimsb-sys02.mdc-berlin.net>
[not found] ` <87r3hw2blw.fsf@gnu.org>
2016-01-06 16:28 ` Ludovic Courtès [this message]
2016-01-06 16:40 ` bug#22273: “guix download” fails with “bad-response” Ricardo Wurmus
2016-08-07 11:14 ` Andy Wingo
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87oacyfz9q.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=22273@debbugs.gnu.org \
--cc=ricardo.wurmus@mdc-berlin.de \
/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).