From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org, ukleinek@informatik.uni-freiburg.de,
jimb@codesourcery.com
Subject: Re: [rfa] Clarify remote protocol RLE example
Date: Sun, 16 Dec 2007 22:57:00 -0000 [thread overview]
Message-ID: <uir2yjlxn.fsf@gnu.org> (raw)
In-Reply-To: <20071216203035.GD22905@caradoc.them.org> (message from Daniel Jacobowitz on Sun, 16 Dec 2007 15:30:35 -0500)
> Date: Sun, 16 Dec 2007 15:30:35 -0500
> From: Daniel Jacobowitz <drow@false.org>
> Cc: gdb-patches@sourceware.org, ukleinek@informatik.uni-freiburg.de,
> jimb@codesourcery.com
>
> When I put everything together, I came up with the attached patch. Is
> this clearer?
Yes, thanks.
next prev parent reply other threads:[~2007-12-16 22:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-03 16:20 Daniel Jacobowitz
2007-11-03 18:43 ` Eli Zaretskii
2007-11-03 19:02 ` Eli Zaretskii
2007-11-03 19:18 ` Daniel Jacobowitz
2007-11-03 22:08 ` Eli Zaretskii
2007-11-04 4:03 ` Eli Zaretskii
2007-12-16 20:33 ` Daniel Jacobowitz
2007-12-16 22:57 ` Eli Zaretskii [this message]
2007-12-16 23:01 ` Daniel Jacobowitz
2007-11-06 18:31 ` Jim Blandy
2007-11-07 19:33 ` Michael Snyder
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=uir2yjlxn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=jimb@codesourcery.com \
--cc=ukleinek@informatik.uni-freiburg.de \
/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