Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hui Zhu <teawater@gmail.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [PREC/RFA] Add not_replay to make precord support release memory  	better
Date: Tue, 04 Aug 2009 01:50:00 -0000	[thread overview]
Message-ID: <daef60380908031849l36f91517hb372bf18edc25059@mail.gmail.com> (raw)
In-Reply-To: <4A771EA8.80002@vmware.com>

On Tue, Aug 4, 2009 at 01:30, Michael Snyder<msnyder@vmware.com> wrote:
> Hui Zhu wrote:
>>
>> The record_exec_entry don't have big contact with core dump patch.
>>
>> I think the new version is more clear.
>
> But we had this patch all worked out, and now you've added
> a bunch of new stuff to it.  It's not a "new version" of the
> "add not_replay" patch, it's a whole new change.
>
> That's not the way we do it.  If you want to add new stuff,
> you start a new thread, you don't add it into a thread that's
> already in review.
>
>

OK.  I got it.

So the patch http://sourceware.org/ml/gdb-patches/2009-08/msg00006.html
looks OK.
Could you check it in?

I will update dump patch after this patch in.

Thanks,
Hui


  reply	other threads:[~2009-08-04  1:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-21 15:39 Hui Zhu
2009-07-24 11:31 ` Michael Snyder
2009-07-24 13:00   ` Hui Zhu
2009-07-25 20:56     ` Michael Snyder
2009-07-27 16:18       ` Hui Zhu
2009-08-01 23:01         ` Michael Snyder
2009-08-02  4:11           ` Hui Zhu
2009-08-03  3:51             ` Hui Zhu
2009-08-03  5:02               ` Michael Snyder
2009-08-03  5:19                 ` Hui Zhu
2009-08-03 17:31                   ` Michael Snyder
2009-08-04  1:50                     ` Hui Zhu [this message]
2009-08-04 18:19                       ` Michael Snyder
2009-08-05  1:26                         ` Hui Zhu

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=daef60380908031849l36f91517hb372bf18edc25059@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