From: Aaron Merey <amerey@redhat.com>
To: Andrew Burgess <aburgess@redhat.com>
Cc: gdb-patches@sourceware.org, Simon Marchi <simark@simark.ca>,
Mark Wielaard <mark@klomp.org>
Subject: Re: [PATCHv2] gdb/debuginfod: cleanup debuginfod earlier
Date: Thu, 8 Jun 2023 17:08:22 -0400 [thread overview]
Message-ID: <CAJDtP-QQLBivT5Cd=xT3bQL-H7ON3293uE5CzRPEOPzJALbdbQ@mail.gmail.com> (raw)
In-Reply-To: <a6d031964ed8cba24035c3062f2b5f91fd0a6faf.1686231184.git.aburgess@redhat.com>
On Thu, Jun 8, 2023 at 9:34 AM Andrew Burgess <aburgess@redhat.com> wrote:
>
> It's not obvious how this issue can easily be tested for. The bug does
> not appear to manifest when using a local debuginfod server, so we'd
> need to setup something more involved. For now I'm proposing this
> patch without any associated tests.
LGTM. Tested manually on F37.
Thanks,
Aaron
next prev parent reply other threads:[~2023-06-08 21:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 11:23 [PATCH] " Andrew Burgess
2023-05-23 12:31 ` Simon Marchi
2023-05-23 14:23 ` Aaron Merey
2023-05-24 14:33 ` Andrew Burgess
2023-06-08 13:33 ` [PATCHv2] " Andrew Burgess
2023-06-08 15:09 ` Mark Wielaard
2023-06-08 21:08 ` Aaron Merey [this message]
2023-06-09 14:24 ` Tom Tromey
2023-06-09 14:38 ` Andrew Burgess
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='CAJDtP-QQLBivT5Cd=xT3bQL-H7ON3293uE5CzRPEOPzJALbdbQ@mail.gmail.com' \
--to=amerey@redhat.com \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=mark@klomp.org \
--cc=simark@simark.ca \
/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).