From: Doug Evans <dje@sebabeach.org>
To: binutils@sources.redhat.com, cgen@sources.redhat.com
Subject: some opcode files could be regenerated (e.g. <cpu>-desc.c)
Date: Sat, 19 Apr 2003 18:27:00 -0000 [thread overview]
Message-ID: <20030419173752.8DE12B53A@seba.sebabeach.org> (raw)
Setting aside the copyright date changes, it'd be useful to
regenerate the -desc.c files.
I'm testing some changes and there's a lot of noise in the diffs.
Anyone mind?
next reply other threads:[~2003-04-19 18:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-19 18:27 Doug Evans [this message]
2003-04-20 8:52 ` Nick Clifton
2003-04-20 15:52 ` Doug Evans
2003-04-21 9:13 ` Nick Clifton
2003-04-22 18:53 ` Doug Evans
2003-04-23 8:15 ` Nick Clifton
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=20030419173752.8DE12B53A@seba.sebabeach.org \
--to=dje@sebabeach.org \
--cc=binutils@sources.redhat.com \
--cc=cgen@sources.redhat.com \
/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).