From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: teawater <teawater@gmail.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA] Resubmit process record and replay, 8/10
Date: Thu, 20 Nov 2008 12:08:00 -0000 [thread overview]
Message-ID: <1227155039.28256.115.camel@localhost.localdomain> (raw)
In-Reply-To: <4924C55D.2050802@vmware.com>
El mié, 19-11-2008 a las 18:03 -0800, Michael Snyder escribió:
> Hmm, I'm not the master of protocol here (Joel?), but my impression
> is that we would prefer to see the diffs against the current CVS, not
> against the previous patch.
Actually, he sent the diff against CVS as an attachment, and a diff
against the previous patch inline.
> If there's important changes since the previous patch, could you
> maybe include a brief description of the changes?
From what I could see, he made many messages be printed only if
record_debug is set, and expanded all case A..B instances, to be ISO C
compliant.
--
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center
prev parent reply other threads:[~2008-11-20 4:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-17 7:04 teawater
2008-11-20 5:56 ` Michael Snyder
2008-11-20 12:08 ` Thiago Jung Bauermann [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=1227155039.28256.115.camel@localhost.localdomain \
--to=bauerman@br.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.com \
--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