From: Steven Johnson <sbjohnson@ozemail.com.au>
To: gdb@sourceware.cygnus.com
Subject: regcache.c/regcache.h
Date: Fri, 08 Sep 2000 04:54:00 -0000 [thread overview]
Message-ID: <39B8D31B.FF625798@ozemail.com.au> (raw)
In-Reply-To: <396F162A.6D9F0628@ozemail.com.au>
Ive grown sick of regcache.c having it's definitions spread across half
a dozen different headers.
Is there any good reason why I shouldn't collate this stuff into a
single header, and call it for arguments sake regcache.h?
In anticipation of the answer being "Sounds good to me" I have already
started this. hoping to have it finished tonight. (If i can remain
conscious)
Steven.
next prev parent reply other threads:[~2000-09-08 4:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-14 0:33 rs6000-tdep Steven Johnson
2000-07-14 1:34 ` rs6000-tdep Andrew Cagney
2000-07-14 5:35 ` rs6000-tdep Steven Johnson
2000-07-14 6:20 ` rs6000-tdep Andrew Cagney
2000-07-14 6:32 ` rs6000-tdep Steven Johnson
2000-07-14 7:54 ` rs6000-tdep Nick Duffek
2000-07-14 8:02 ` rs6000-tdep Kevin Buettner
2000-07-14 15:20 ` rs6000-tdep Nick Duffek
2000-07-15 0:38 ` rs6000-tdep - Further Developments Steven Johnson
2000-07-15 7:59 ` Fernando Nasser
2000-09-08 4:54 ` Steven Johnson [this message]
2000-09-08 6:23 ` regcache.c/regcache.h Steven Johnson
2000-07-14 6:26 ` rs6000-tdep Mark Kettenis
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=39B8D31B.FF625798@ozemail.com.au \
--to=sbjohnson@ozemail.com.au \
--cc=gdb@sourceware.cygnus.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).