From: Daniel Jacobowitz <drow@mvista.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: ac131313@cygnus.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA] gdbserver 2/3 - platform config
Date: Fri, 15 Feb 2002 08:04:00 -0000 [thread overview]
Message-ID: <20020215110447.B21634@nevyn.them.org> (raw)
In-Reply-To: <200202141022.MAA28635@is.elta.co.il>
On Thu, Feb 14, 2002 at 12:22:33PM +0200, Eli Zaretskii wrote:
> > Date: Thu, 14 Feb 2002 00:51:39 -0500
> > From: Daniel Jacobowitz <drow@mvista.com>
> >
> > Committed. Same caveats about broken tree as with the previous patch,
> > and same promise about NEWS.
>
> _Please_ consider the documentation of this as well.
Well, NEWS definitely needs updating, as does gdbserver/README. So
does gdbserver's man page, for --attach, since I missed that. The rest
of the documentation should be OK.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2002-02-15 16:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-05 14:48 Daniel Jacobowitz
2002-02-13 20:24 ` Andrew Cagney
2002-02-13 21:51 ` Daniel Jacobowitz
2002-02-14 2:23 ` Eli Zaretskii
2002-02-15 8:04 ` 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=20020215110447.B21634@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@cygnus.com \
--cc=eliz@is.elta.co.il \
--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