From: "Eli Zaretskii" <eliz@elta.co.il>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [cplus] Add an entry point for cp-names
Date: Sun, 29 Feb 2004 18:05:00 -0000 [thread overview]
Message-ID: <3405-Sun29Feb2004200449+0200-eliz@elta.co.il> (raw)
In-Reply-To: <20040229172545.GL15749@nevyn.them.org> (message from Daniel Jacobowitz on Sun, 29 Feb 2004 12:25:45 -0500)
> Date: Sun, 29 Feb 2004 12:25:45 -0500
> From: Daniel Jacobowitz <drow@mvista.com>
>
> My point was that I couldn't make heads or tails out of what the sed
> script was doing, but I'm willing to follow instructions :) I've
> checked in this to drow-cplus-branch. Do you think I need to tweak
> anything further?
No, I think this is fine. I will get to it in due time and fix
anything that needs fixing.
Thanks.
prev parent reply other threads:[~2004-02-29 18:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-24 22:36 Daniel Jacobowitz
2004-01-04 6:16 ` Eli Zaretskii
2004-02-09 20:34 ` Daniel Jacobowitz
2004-02-10 6:36 ` Eli Zaretskii
2004-02-29 17:25 ` Daniel Jacobowitz
2004-02-29 18:05 ` 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=3405-Sun29Feb2004200449+0200-eliz@elta.co.il \
--to=eliz@elta.co.il \
--cc=drow@mvista.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