From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch 00/12] entryval#2: Fix x86_64 <optimized out> parameters, virtual tail call frames
Date: Wed, 14 Sep 2011 10:50:00 -0000 [thread overview]
Message-ID: <20110914104446.GA9912@host1.jankratochvil.net> (raw)
In-Reply-To: <E1R3llK-0004ry-As@fencepost.gnu.org>
On Wed, 14 Sep 2011 11:28:10 +0200, Eli Zaretskii wrote:
> > Here is attached a diff against the previous patch series. The changes are:
>
> Sorry, I'm confused: am I supposed to review only the diffs in this
> message and forget about the rest of the series? If no, which parts
> should I review?
I have marked the parts to review with `+doc' in the subject.
> For now, here are the comments about this part alone:
I did not expect you would review this part but as the original patchset docs
were reviewed it is also a possible way, so everything is OK this way.
I will incorporate the suggestions and I will reply the specific patch parts
with them.
Thanks,
Jan
next prev parent reply other threads:[~2011-09-14 10:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-13 19:44 Jan Kratochvil
2011-09-14 10:26 ` Eli Zaretskii
2011-09-14 10:50 ` Jan Kratochvil [this message]
2011-09-16 9:44 ` Jan Kratochvil
2011-09-17 13:42 ` Eli Zaretskii
2011-09-19 18:30 ` Jan Kratochvil
2011-09-30 0:02 ` obsolete: " Jan Kratochvil
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=20110914104446.GA9912@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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