From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [v2] Re: RFA/RFC: vCont for the remote protocol [doco]
Date: Fri, 10 Oct 2003 02:21:00 -0000 [thread overview]
Message-ID: <3F8617AA.7000908@redhat.com> (raw)
In-Reply-To: <3F7AE57C.3080100@redhat.com>
> Looks good. Can you send it as a formal proposal (as a protocol change) to gdb@, then give it a week?
(Sigh of relief, didn't raise an eyebrow! :-)
I'm ok with this doco, but check with Eli for the texinfo side of things
(my be easier to just post the final texinfo).
Andrew
prev parent reply other threads:[~2003-10-10 2:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-29 15:29 Daniel Jacobowitz
2003-09-29 21:17 ` Andrew Cagney
2003-09-29 21:25 ` Daniel Jacobowitz
2003-09-30 14:37 ` Andrew Cagney
2003-09-30 14:51 ` Daniel Jacobowitz
2003-09-30 15:37 ` Andrew Cagney
2003-09-30 21:16 ` [v2] " Daniel Jacobowitz
2003-10-01 14:32 ` Andrew Cagney
2003-10-10 2:21 ` Andrew Cagney [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=3F8617AA.7000908@redhat.com \
--to=ac131313@redhat.com \
--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