From: Aaron Merey <amerey@redhat.com>
To: aburgess@redhat.com
Cc: Eli Zaretskii <eliz@gnu.org>,
gdb-patches@sourceware.org, mliska@suse.cz, tdevries@suse.de,
keiths@redhat.com
Subject: Re: [PATCH v4] gdb/debuginfod: Ctrl-C asks to cancel further downloads
Date: Fri, 28 Jun 2024 16:37:16 -0400 [thread overview]
Message-ID: <CAJDtP-Qv0K0mG6wD2uK2yZu0q0LdSYUOTb3Q5zbcvD8o=2PkSA@mail.gmail.com> (raw)
In-Reply-To: <CAJDtP-S-xk3Z6i9JivWsmtNsuOHWfXb5AD12vqTA=rFEhjLTtw@mail.gmail.com>
On Fri, Jun 14, 2024 at 2:22 PM Aaron Merey <amerey@redhat.com> wrote:
>
> On Wed, Jun 12, 2024 at 3:23 AM Eli Zaretskii <eliz@gnu.org> wrote:
> >
> > > From: Aaron Merey <amerey@redhat.com>
> > > Cc: gdb-patches@sourceware.org,
> > > mliska@suse.cz,
> > > tdevries@suse.de,
> > > keiths@redhat.com,
> > > Aaron Merey <amerey@redhat.com>,
> > > Eli Zaretskii <eliz@gnu.org>
> > > Date: Tue, 11 Jun 2024 16:56:12 -0400
> > >
> > > I changed the user_data constructor to call target_terminal::is_ours
> > > since this results in slightly less code duplication.
> > >
> > > I've updated patch below with this change as well as UI text change
> > > that Keith suggested.
> >
> > Thanks, the documentation parts are okay.
> >
> > Reviewed-By: Eli Zaretskii <eliz@gnu.org>
>
> Ok to merge?
Ping. Ok to merge?
Aaron
prev parent reply other threads:[~2024-06-28 20:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-03 2:15 Aaron Merey
2024-02-22 22:26 ` [PING][PATCH " Aaron Merey
2024-02-23 7:52 ` Eli Zaretskii
2024-03-01 0:12 ` [PING*2][PATCH " Aaron Merey
2024-05-17 14:11 ` Aaron Merey
2024-05-31 20:57 ` [PING*3][PATCH " Aaron Merey
2024-06-07 20:48 ` [PING*4][PATCH " Aaron Merey
2024-06-07 23:27 ` Keith Seitz
2024-06-10 16:55 ` Aaron Merey
2024-06-11 11:43 ` [PATCH " Andrew Burgess
2024-06-11 20:56 ` Aaron Merey
2024-06-12 7:23 ` Eli Zaretskii
2024-06-14 18:22 ` Aaron Merey
2024-06-28 20:37 ` Aaron Merey [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='CAJDtP-Qv0K0mG6wD2uK2yZu0q0LdSYUOTb3Q5zbcvD8o=2PkSA@mail.gmail.com' \
--to=amerey@redhat.com \
--cc=aburgess@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=keiths@redhat.com \
--cc=mliska@suse.cz \
--cc=tdevries@suse.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).