From: Tom Tromey <tom@tromey.com>
To: Alan Modra <amodra@gmail.com>
Cc: Tom Tromey <tom@tromey.com>,
Alan Modra via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: sim prune_warnings
Date: Thu, 31 Aug 2023 21:07:03 -0600 [thread overview]
Message-ID: <87zg261tig.fsf@tromey.com> (raw)
In-Reply-To: <ZPEQVckU2MXULnlU@squeak.grove.modra.org> (Alan Modra's message of "Fri, 1 Sep 2023 07:42:37 +0930")
Alan> I committed the patch on Aug 19, when pushing the sim regen series.
Alan> It seemed obvious enough to me. Without it I would have needed to
Alan> edit commit 9d4f36166d626 log to report a lot more fails.
Ok, thanks. I sometimes reply to patches when I haven't seen any
traffic; I didn't think to check the git log.
Tom
next prev parent reply other threads:[~2023-09-01 3:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 8:13 Alan Modra
2023-08-31 13:25 ` Tom Tromey
2023-08-31 22:12 ` Alan Modra
2023-09-01 3:07 ` Tom Tromey [this message]
2023-10-15 9:38 ` Mike Frysinger
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=87zg261tig.fsf@tromey.com \
--to=tom@tromey.com \
--cc=amodra@gmail.com \
--cc=gdb-patches@sourceware.org \
/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).