From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: ac131313@ges.redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/doco] Revise "Include Files" in internals doco
Date: Wed, 31 Jul 2002 03:47:00 -0000 [thread overview]
Message-ID: <9003-Wed31Jul2002131451+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <3D46B233.6090201@ges.redhat.com> (message from Andrew Cagney on Tue, 30 Jul 2002 11:35:15 -0400)
> Date: Tue, 30 Jul 2002 11:35:15 -0400
> From: Andrew Cagney <ac131313@ges.redhat.com>
>
> This tries to clarify GDB's include file coding policy. It now makes a
> direct reference to opaque structures.
>
> The rules haven't actually changes.
>
> ok?
Yes, thanks.
next prev parent reply other threads:[~2002-07-31 10:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-30 8:42 Andrew Cagney
2002-07-31 3:47 ` Eli Zaretskii [this message]
2002-08-01 9:50 ` 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=9003-Wed31Jul2002131451+0300-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=ac131313@ges.redhat.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