From: Tom Tromey <tom@tromey.com>
To: Mark Wielaard <mark@klomp.org>
Cc: Enze Li <enze.li@hotmail.com>,
gdb-patches@sourceware.org, Simon Marchi <simark@simark.ca>,
Sam James <sam@gentoo.org>
Subject: Re: [PATCHv2] gdb: Ignore some stringop-overflow and restrict warnings on sparc
Date: Tue, 24 Jan 2023 08:25:40 -0700 [thread overview]
Message-ID: <87cz74vtsb.fsf@tromey.com> (raw)
In-Reply-To: <20230124093541.GE11538@gnu.wildebeest.org> (Mark Wielaard's message of "Tue, 24 Jan 2023 10:35:41 +0100")
>>>>> "Mark" == Mark Wielaard <mark@klomp.org> writes:
Mark> Ah, too bad :{ I really like ChangeLog entries for (self) review of
Mark> patches. Do you want me to post a V3 without them?
No need to repost.
You should probably leave include/ChangeLog in place.
Tom
next prev parent reply other threads:[~2023-01-24 15:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 0:44 Mark Wielaard
2023-01-24 3:32 ` Enze Li
2023-01-24 9:35 ` Mark Wielaard
2023-01-24 15:25 ` Tom Tromey [this message]
2023-01-24 15:19 ` Tom Tromey
2023-01-24 15:22 ` Tom Tromey
2023-01-24 15:25 ` Tom Tromey
2023-01-24 19:26 ` 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=87cz74vtsb.fsf@tromey.com \
--to=tom@tromey.com \
--cc=enze.li@hotmail.com \
--cc=gdb-patches@sourceware.org \
--cc=mark@klomp.org \
--cc=sam@gentoo.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).