From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: eliz@gnu.org
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc] [0/9] Cell multi-arch debugger
Date: Thu, 23 Jul 2009 15:39:00 -0000 [thread overview]
Message-ID: <200907231209.n6NC986W012886@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <83zlaw4miw.fsf@gnu.org> from "Eli Zaretskii" at Jul 22, 2009 09:09:59 PM
Eli Zaretskii wrote:
> > Date: Wed, 22 Jul 2009 19:14:00 +0200 (CEST)
> > From: "Ulrich Weigand" <uweigand@de.ibm.com>
> > Cc: eliz@gnu.org
> >
> > Eli, I think I've addressed in the documentation changes all issues you
> > raised when I last posted the patch series. I've also now added NEWS
> > entries where appropriate. Are the docu/NEWS changes OK?
>
> Yes, with a few minor comments. See the responses to the individual
> patches in this set.
Thanks for the quick review!
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2009-07-23 12:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 17:15 Ulrich Weigand
2009-07-22 18:11 ` Eli Zaretskii
2009-07-23 15:39 ` Ulrich Weigand [this message]
2009-07-31 18:29 ` Ulrich Weigand
2009-08-03 16:11 ` Thiago Jung Bauermann
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=200907231209.n6NC986W012886@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.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