From: zimoun <zimon.toutoune@gmail.com>
To: Julien Lepiller <julien@lepiller.eu>,
Tobias Geerinckx-Rice <me@tobias.gr>
Cc: "Ludovic Courtès" <ludo@gnu.org>, 26489@debbugs.gnu.org
Subject: [bug#26489] [PATCH] substitute: Ignore bad responses.
Date: Tue, 09 Feb 2021 02:05:34 +0100 [thread overview]
Message-ID: <86v9b2jbj5.fsf@gmail.com> (raw)
In-Reply-To: <20210115205224.7f775008@tachikoma.lepiller.eu> (Julien Lepiller's message of "Fri, 15 Jan 2021 20:52:24 +0100")
Hi,
On Fri, 15 Jan 2021 at 20:52, Julien Lepiller <julien@lepiller.eu> wrote:
> Le Mon, 11 Jan 2021 14:08:22 +0100,
> zimoun <zimon.toutoune@gmail.com> a écrit :
>> On Sun, 20 Dec 2020 at 14:39, Ludovic Courtès <ludo@gnu.org> wrote:
>>
>> >>> I’d be happy with a patch along these lines!
>> >>
>> >> Tobias, do you plan to rework/rebase it?
>> >
>> > In the meantime, commit 5ff521452b9ec2aae9ed8e4bb7bdc250a581f203
>> > added ‘bad-response’ handling (and more). We should take a closer
>> > look, but it may be that this issue is now addressed.
>>
>> Since you reported the use-case and the patch, could you confirm that
>> the commit 5ff521 addresses the issue?
>>
>> I think it does but maybe I am missing something; probably I am. :-)
>
> It seems not, since a few days ago we had exactly that problem. See
> https://issues.guix.gnu.org/45828
Bug#45828 is now closed. I think it makes sense to close this one too.
If no objection, I am proposing to close this old bug. :-)
Cheers,
simon
next prev parent reply other threads:[~2021-02-09 1:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-14 0:27 bug#26489: [PATCH] substitute: Ignore bad responses Tobias Geerinckx-Rice
2017-04-14 9:54 ` Ludovic Courtès
2017-04-28 20:56 ` Tobias Geerinckx-Rice
2017-05-01 13:14 ` Ludovic Courtès
2020-12-18 20:19 ` [bug#26489] " zimoun
2020-12-20 13:39 ` Ludovic Courtès
2021-01-11 13:08 ` zimoun
2021-01-15 19:52 ` Julien Lepiller
2021-02-09 1:05 ` zimoun [this message]
2021-02-09 8:42 ` bug#26489: " 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
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=86v9b2jbj5.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=26489@debbugs.gnu.org \
--cc=julien@lepiller.eu \
--cc=ludo@gnu.org \
--cc=me@tobias.gr \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).