From: Daniel Jacobowitz <dan@codesourcery.com>
To: Stefan Weil <weil@mail.berlios.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Fix a parallel build failure.
Date: Wed, 4 Nov 2009 15:58:25 -0500 [thread overview]
Message-ID: <20091104205825.GA11267@caradoc.them.org> (raw)
In-Reply-To: <4AF1E896.4060606@mail.berlios.de>
On Wed, Nov 04, 2009 at 09:48:22PM +0100, Stefan Weil wrote:
> Maybe a mix of your patch and my patch
> (http://patchwork.ozlabs.org/patch/37446/)
> would be the best fix for this problem.
>
> It should also be possible to apply both patches.
Thanks, I didn't find your patch. I don't have any preference which
is applied, although I'm always in favor of eliminating unnecessary
recursive invocations.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2009-11-04 20:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 20:20 [Qemu-devel] [PATCH] Fix a parallel build failure Daniel Jacobowitz
2009-11-04 20:48 ` Stefan Weil
2009-11-04 20:58 ` Daniel Jacobowitz [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=20091104205825.GA11267@caradoc.them.org \
--to=dan@codesourcery.com \
--cc=qemu-devel@nongnu.org \
--cc=weil@mail.berlios.de \
/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;
as well as URLs for NNTP newsgroup(s).