From: "Frank Ch. Eigler" <fche@redhat.com>
To: Alan Modra <amodra@gmail.com>
Cc: cgen@sourceware.org, vapier@gentoo.org
Subject: Re: sim: update to reduce generated file differences
Date: Thu, 10 Aug 2023 10:21:13 -0400 [thread overview]
Message-ID: <20230810142113.GA12318@redhat.com> (raw)
In-Reply-To: <ZNSBCrHzk+Yttfql@squeak.grove.modra.org>
Hi -
> Put binutils-gdb commit db7858e227f3 (Mike Frysinger 2015-06-12) and
> 13a590ca65f7 (Mike Frysinger 2017-02-13) in the source rather than
> generated files.
Please feel free to commit changes this obvious.
- FChE
prev parent reply other threads:[~2023-08-10 14:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 6:17 Alan Modra
2023-08-10 14:21 ` Frank Ch. Eigler [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=20230810142113.GA12318@redhat.com \
--to=fche@redhat.com \
--cc=amodra@gmail.com \
--cc=cgen@sourceware.org \
--cc=vapier@gentoo.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).