From: Andrew Cagney <cagney@gnu.org>
To: "Nathan J. Williams" <nathanw@wasabisystems.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [commit] fix to include in alphanbsd-tdep.c
Date: Mon, 10 May 2004 21:02:00 -0000 [thread overview]
Message-ID: <409FE739.5080302@gnu.org> (raw)
In-Reply-To: <mtur7ts2kof.fsf@all-night-tool.mit.edu>
Committed as obvious (but eww, underscores in filenames).
http://sources.redhat.com/gdb/current/onlinedocs/gdbint_13.html#SEC125
When GDB has a local version of a system header file (ex `string.h') the
file name based on the POSIX header prefixed with `gdb_'
(`gdb_string.h'). These headers should be relatively independent: they
should use only macros defined by `configure', the compiler, or the
host; they should include only system headers; they should refer only to
system types. They may be shared between multiple programs, e.g. GDB and
GDBSERVER.
For other files `-' is used as the separator.
next prev parent reply other threads:[~2004-05-10 21:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-10 18:54 Nathan J. Williams
2004-05-10 21:02 ` Andrew Cagney [this message]
2004-05-10 20:51 ` Nathan J. Williams
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=409FE739.5080302@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=nathanw@wasabisystems.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