From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Michael Snyder <Michael.Snyder@palmsource.com>,
gdb-patches@sourceware.org
Subject: Re: [commit] Describe GDB source structure (Was: GDB source structure)
Date: Sat, 02 Sep 2006 15:32:00 -0000 [thread overview]
Message-ID: <20060902153202.GA12737@nevyn.them.org> (raw)
In-Reply-To: <uveo6uvyx.fsf@gnu.org>
On Sat, Sep 02, 2006 at 06:30:46PM +0300, Eli Zaretskii wrote:
> Inspired by the description posted by Michael to gdb@, I committed the
> following change to the gdbint manual:
>
> 2006-09-02 Eli Zaretskii <eliz@gnu.org>
>
> * gdbint.texinfo (Overall Structure): New section "Source Tree
> Structure".
Thank you!
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2006-09-02 15:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ee4c53600609011321k5a7a538fp933250cc13bb58d6@mail.gmail.com>
[not found] ` <ee4c53600609011324u4170f512pe88c25064fca8579@mail.gmail.com>
[not found] ` <1157144236.4466.80.camel@localhost.localdomain>
2006-09-02 15:30 ` Eli Zaretskii
2006-09-02 15:32 ` Daniel Jacobowitz [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=20060902153202.GA12737@nevyn.them.org \
--to=drow@false.org \
--cc=Michael.Snyder@palmsource.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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