From: Kevin Buettner <kevinb@redhat.com>
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: gdb-patches@sourceware.org, Bruno Larsen <blarsen@redhat.com>,
Tom Tromey <tom@tromey.com>
Subject: Re: [PATCH v2] gdb: Modify the output of "info breakpoints" and "delete breakpoints"
Date: Sat, 17 Feb 2024 20:48:03 -0700 [thread overview]
Message-ID: <20240217204803.4eac6e25@f39-zbm-amd> (raw)
In-Reply-To: <57a15230-f85e-f763-c5e2-3c5cb90ddc84@loongson.cn>
Hi Tiezhu,
On Sun, 18 Feb 2024 10:06:48 +0800
Tiezhu Yang <yangtiezhu@loongson.cn> wrote:
> Is it necessary to rebase and update this patch?
> Should I drop it or send a new version?
Please update/rebase this patch and resend.
Also, add me on the CC line...
Kevin
prev parent reply other threads:[~2024-02-18 3:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 9:16 Tiezhu Yang
2022-05-19 13:08 ` Bruno Larsen
2024-02-18 2:06 ` Tiezhu Yang
2024-02-18 3:48 ` Kevin Buettner [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=20240217204803.4eac6e25@f39-zbm-amd \
--to=kevinb@redhat.com \
--cc=blarsen@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
--cc=yangtiezhu@loongson.cn \
/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).