All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: George Dunlap <george.dunlap@eu.citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>, Olaf Hering <olaf@aepfle.de>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	xen-devel@lists.xen.org
Subject: Re: [PATCH v2] tools/mkrpm: improve version.release handling
Date: Mon, 30 Mar 2015 10:08:48 +0100	[thread overview]
Message-ID: <1427706528.13935.224.camel@citrix.com> (raw)
In-Reply-To: <5512BFC7.4010403@eu.citrix.com>

On Wed, 2015-03-25 at 14:01 +0000, George Dunlap wrote:

> Reviewed-by: George Dunlap <george.dunlap@eu.citrix.com>
> Tested-by: George Dunlap <george.dunlap@eu.citrix.com>

Applied, thanks.

      parent reply	other threads:[~2015-03-30  9:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-24 14:37 [PATCH v2] tools/mkrpm: improve version.release handling Olaf Hering
2015-03-25 14:01 ` George Dunlap
2015-03-26  7:39   ` Olaf Hering
2015-03-30  9:08   ` Ian Campbell [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=1427706528.13935.224.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=olaf@aepfle.de \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=wei.liu2@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.