From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: Re: "gdb_XXX.h" include files
Date: Mon, 03 Mar 2003 18:52:00 -0000 [thread overview]
Message-ID: <3E63A479.2050009@redhat.com> (raw)
In-Reply-To: <20030303045244.GA8045@nevyn.them.org>
> Andrew, per an earlier conversation, you said this:
>
>
>> I think it would be easier to just clarify the guidelines for
>> ``gdb_XXXX.h'' files - that they be independant as they are included by
>> GDB and friends.
>
>
> How'd you feel about documenting this in gdbint.texinfo? Good idea, bad
> idea?
Pointer to original thread?
next prev parent reply other threads:[~2003-03-03 18:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-03 4:52 Daniel Jacobowitz
2003-03-03 18:52 ` Andrew Cagney [this message]
2003-03-03 19:04 ` Daniel Jacobowitz
2003-03-13 20:36 ` Andrew Cagney
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=3E63A479.2050009@redhat.com \
--to=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=gdb@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