From: Andrew Cagney <ac131313@cygnus.com>
To: jtc@redback.com
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: [RFC]: More include file cleanup
Date: Thu, 22 Mar 2001 18:20:00 -0000 [thread overview]
Message-ID: <3ABAB2F0.F2032C72@cygnus.com> (raw)
In-Reply-To: <5m8zm09gtr.fsf@jtc.redback.com>
J.T.
I'm in two minds on this. Either a) it should be left until after 5.1
(.....) or b) it should go in regardless.
My main reason for having cold feet is from the experience learnt from
regcache.h.
Andrew
prev parent reply other threads:[~2001-03-22 18:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-20 15:11 J.T. Conklin
2001-03-22 18:20 ` Andrew Cagney [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=3ABAB2F0.F2032C72@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sourceware.cygnus.com \
--cc=jtc@redback.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