From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Re: Internals manual update
Date: Sun, 22 Jun 2008 04:19:00 -0000 [thread overview]
Message-ID: <20080622041854.GA2955@caradoc.them.org> (raw)
In-Reply-To: <ulk0yf92h.fsf@gnu.org>
On Sun, Jun 22, 2008 at 06:21:58AM +0300, Eli Zaretskii wrote:
> > Date: Sat, 21 Jun 2008 15:42:10 -0700
> > From: Stan Shebs <stanshebs@earthlink.net>
> >
> > So as I've been refreshing my memory about GDB code, I've also been
> > going through the internals manual and making it be more consistent with
> > the current state of things.
>
> Thanks!
Ditto - this is great.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2008-06-22 4:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-21 22:42 Stan Shebs
2008-06-22 3:22 ` Eli Zaretskii
2008-06-22 4:19 ` 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=20080622041854.GA2955@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@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