From: fche@redhat.com (Frank Ch. Eigler)
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Basic structure to describe register formats
Date: Fri, 01 Feb 2002 14:01:00 -0000 [thread overview]
Message-ID: <o57kpw6evc.fsf@toenail.toronto.redhat.com> (raw)
In-Reply-To: <20020201162042.A20026@nevyn.them.org>
Daniel Jacobowitz <drow@mvista.com> writes:
> [...]
> > Any way I think EXPEDITE to better word for describing what is to be
> > done with those registers. SID uses that word to describe this exact
> > same list.
>
> That's a good word for what's going on here, I quite like it. [...]
BTW, sid folks don't deserve credit for picking the word. Methinks
Stu Grossman wrote it into gdb ~8 years ago.
- FChE
prev parent reply other threads:[~2002-02-01 22:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-01 12:22 Daniel Jacobowitz
2002-02-01 13:10 ` Andrew Cagney
2002-02-01 13:21 ` Daniel Jacobowitz
2002-02-01 13:50 ` Andrew Cagney
2002-02-01 14:09 ` Daniel Jacobowitz
2002-02-01 15:28 ` Andrew Cagney
2002-02-01 14:01 ` 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=o57kpw6evc.fsf@toenail.toronto.redhat.com \
--to=fche@redhat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@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