Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: teawater <teawater@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA reverse] Process record and replay target user docs for gdb manual
Date: Fri, 03 Oct 2008 06:26:00 -0000	[thread overview]
Message-ID: <uiqsai494.fsf@gnu.org> (raw)
In-Reply-To: <daef60380810020223j71ae22a9j2b55bb4183d86ca9@mail.gmail.com>

> Date: Thu, 2 Oct 2008 17:23:57 +0800
> From: teawater <teawater@gmail.com>
> 
> This is process record and replay target user manual.

Thank you.

Please remind me the context of this text.  Does it describe
additional aspects of the patches posted just yesterday by Michael
Snyder?  Or does it describe some other GDB feature?  Or something
else?

Armed with that knowledge, I will know what to do with this text and
when.

Thanks.


  reply	other threads:[~2008-10-03  6:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-02  9:24 teawater
2008-10-03  6:26 ` Eli Zaretskii [this message]
2008-10-03  9:15   ` teawater
2008-10-03 10:06     ` Eli Zaretskii
2008-10-03 15:46   ` Michael Snyder
2008-12-11  5:53     ` moueza
2008-12-11  6:20       ` teawater
2008-12-11 17:57         ` 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=uiqsai494.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=teawater@gmail.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