From: Eli Zaretskii <eliz@is.elta.co.il>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: Re: New branch ``drow-cplus-branch''
Date: Sun, 06 Oct 2002 22:59:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1021007075808.6644D-100000@is> (raw)
In-Reply-To: <20021006032037.GA28685@nevyn.them.org>
On Sat, 5 Oct 2002, Daniel Jacobowitz wrote:
> I've created a branch for the C++ and namespace improvements David and I
> were discussing.
Thanks for working on this.
I'd like to suggest that you try to document the necessary details in
gdbint.texinfo as well, as you go. (If you need help in looking through
your Texinfo, send the patches to me.) That way, we won't face a huge
problem of documenting a large body of new code when the branch is merged
with HEAD.
Just my $0.02.
prev parent reply other threads:[~2002-10-07 5:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-05 20:20 Daniel Jacobowitz
2002-10-06 22:59 ` Eli Zaretskii [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=Pine.SUN.3.91.1021007075808.6644D-100000@is \
--to=eliz@is.elta.co.il \
--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