xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH] tools/vtpm: fix tpm_version.h error during parallel build
Date: Thu, 2 Aug 2012 17:54:01 +0200	[thread overview]
Message-ID: <20120802155401.GA10748@aepfle.de> (raw)
In-Reply-To: <1343724173.15432.70.camel@zakaz.uk.xensource.com>

On Tue, Jul 31, Ian Campbell wrote:

> I've just seen the original thread which points out that fixing this in
> that way requires patching the downloaded source while this solution
> requires only that we patch our own Makefile.
> 
> It would have been useful to note this in the commit message.

I just sent another version with updated commit message.

Olaf

  reply	other threads:[~2012-08-02 15:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-31  8:12 [PATCH] tools/vtpm: fix tpm_version.h error during parallel build Olaf Hering
2012-07-31  8:34 ` Ian Campbell
2012-07-31  8:42   ` Ian Campbell
2012-08-02 15:54     ` Olaf Hering [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-08-02 15:53 Olaf Hering
2012-08-03  8:55 ` Ian Campbell

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=20120802155401.GA10748@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=Ian.Campbell@citrix.com \
    --cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).