From: Daniel Jacobowitz <drow@mvista.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: FYI: gdbserver branch merges
Date: Sat, 30 Mar 2002 21:48:00 -0000 [thread overview]
Message-ID: <20020331004840.A23003@nevyn.them.org> (raw)
In-Reply-To: <Pine.SUN.3.91.1020331073719.14188G@is>
On Sun, Mar 31, 2002 at 07:41:08AM +0200, Eli Zaretskii wrote:
>
> On Fri, 29 Mar 2002, Daniel Jacobowitz wrote:
>
> > I've moved these patches to the branch.
>
> Does the manual need any changes as result of these merges? If so,
> could you please submit the changes for the docs as well?
>
> TIA
No, it doesn't. Thanks for checking.
I still owe a NEWS entry about gdbserver; I'll do that in a day or two.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-03-31 5:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-29 11:10 Daniel Jacobowitz
2002-03-29 11:32 ` Andreas Jaeger
2002-03-29 11:38 ` Daniel Jacobowitz
2002-04-03 18:59 ` Andrew Cagney
2002-03-30 21:42 ` Eli Zaretskii
2002-03-30 21:48 ` Daniel Jacobowitz [this message]
2002-04-03 18:59 ` Andrew Cagney
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=20020331004840.A23003@nevyn.them.org \
--to=drow@mvista.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