From: Doug Evans <dje@transmeta.com>
To: fche@redhat.com
Cc: cgen@sources.redhat.com
Subject: insn-word-bitsize
Date: Mon, 09 Jul 2001 16:19:00 -0000 [thread overview]
Message-ID: <200107092319.QAA19491@casey.transmeta.com> (raw)
I wrote:
>Ah. Then I don't have a problem with the patch _providing_
>word[-_]bitsize is renamed (say insn[-_]word[-_]bitsize).
btw, just so there's no misunderstanding,
what I'm suggesting is adding insn-word-bitsize, not replacing word-bitsize
with insn-word-bitsize (i.e. rename word-bitsize in your patch).
Hmmm... I just grepped for it, insn-word-bitsize is already there!
next reply other threads:[~2001-07-09 16:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-09 16:19 Doug Evans [this message]
[not found] <200107092319.QAA19491.cygnus.local.cgen@casey.transmeta.com>
2001-07-10 9:15 ` insn-word-bitsize Frank Ch. Eigler
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=200107092319.QAA19491@casey.transmeta.com \
--to=dje@transmeta.com \
--cc=cgen@sources.redhat.com \
--cc=fche@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).