public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: elfutils-devel@sourceware.org
Subject: Re: PR27859 PATCH: correct 404-latch in connection reuse
Date: Sun, 16 May 2021 17:50:33 -0400	[thread overview]
Message-ID: <20210516215033.GB23897@redhat.com> (raw)
In-Reply-To: <YKGS7bob7xKFxyOq@wildebeest.org>

Hi -

> > (I'll deploy this fix to one of the public servers to confirm it there.)
> 
> Thanks. If that looks good, please commit.

It does, will do.  I'd like to respin rawhide with that patch too.


> It is nice that the multi code works that way, it makes things a bit
> simpler and less state to keep around for the debuginfod_client
> handle. [...]

Yeah.  Unfortunately, it took examining the curl source code (rather
than documentation) through systemtap statement-level tracing to
figure this out.

- FChE


  reply	other threads:[~2021-05-16 21:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-14 22:51 Frank Ch. Eigler
2021-05-16 21:47 ` Mark Wielaard
2021-05-16 21:50   ` Frank Ch. Eigler [this message]
2021-05-17 10:08     ` Mark Wielaard

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=20210516215033.GB23897@redhat.com \
    --to=fche@redhat.com \
    --cc=elfutils-devel@sourceware.org \
    --cc=mark@klomp.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).