From: Mark Wielaard <mark@klomp.org>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: elfutils-devel@sourceware.org
Subject: Re: PR27859 PATCH: correct 404-latch in connection reuse
Date: Mon, 17 May 2021 12:08:25 +0200 [thread overview]
Message-ID: <b6aae0eb79cdafd825fe69617a8ca333776acf31.camel@klomp.org> (raw)
In-Reply-To: <20210516215033.GB23897@redhat.com>
On Sun, 2021-05-16 at 17:50 -0400, Frank Ch. Eigler wrote:
> 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.
Thanks. Maybe we should just do a 0.185 release soon. There is this
issue and the exit code regression for eu-elfcompress when nothing was
done. For both we probably would tell distros to please backport the
fixes. So maybe just help everybody to get a fresh good release?
Cheers,
Mark
prev parent reply other threads:[~2021-05-17 10:08 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
2021-05-17 10:08 ` Mark Wielaard [this message]
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=b6aae0eb79cdafd825fe69617a8ca333776acf31.camel@klomp.org \
--to=mark@klomp.org \
--cc=elfutils-devel@sourceware.org \
--cc=fche@redhat.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).