From: teawater <teawater@gmail.com>
To: "Michael Snyder" <msnyder@vmware.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA] Resubmit process record and replay, 9/10
Date: Thu, 20 Nov 2008 17:09:00 -0000 [thread overview]
Message-ID: <daef60380811200059j13e57f5dw88dee936684d19cd@mail.gmail.com> (raw)
In-Reply-To: <492506A1.2030900@vmware.com>
Never mind. :)
On Thu, Nov 20, 2008 at 14:41, Michael Snyder <msnyder@vmware.com> wrote:
> teawater wrote:
>>
>> This patch is in 9-i386-linux-tdep.txt.
>>
>> I want to add "diff with the previous patch" to make RFA clear. Now, I
>> think it make rfa not clear. Sorry for that.
>
> Understood. Sorry for the confusion.
>
prev parent reply other threads:[~2008-11-20 9:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-17 9:28 teawater
2008-11-20 6:14 ` Michael Snyder
2008-11-20 14:29 ` teawater
2008-11-20 14:51 ` Michael Snyder
2008-11-20 17:09 ` teawater [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=daef60380811200059j13e57f5dw88dee936684d19cd@mail.gmail.com \
--to=teawater@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.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