From: Ian Campbell <Ian.Campbell@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: "Keir (Xen.org)" <keir@xen.org>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: backport requests for 4.x-testing
Date: Wed, 7 Mar 2012 11:38:42 -0800	[thread overview]
Message-ID: <1331149122.14355.4.camel@cthulhu.hellion.org.uk> (raw)
In-Reply-To: <4F573C28.1050305@citrix.com>
On Wed, 2012-03-07 at 05:44 -0500, Andrew Cooper wrote:
> On 07/03/12 09:43, Keir Fraser wrote:
> > On 06/03/2012 11:04, "Andrew Cooper" <andrew.cooper3@citrix.com> wrote:
> >> 24542, 24543, 24570, 24571 (xenoprof fixes)
> > These changesets do not relate to xenoprof??
> 
> So they are not.  It appears that there was an off-by-6 numbering error
> in our patch queue for these patches.  Apologies for that.
These rev numbers are not globally meaningful, you need to use the node
hash if you want to reliably refer to particular changesets.
next prev parent reply	other threads:[~2012-03-07 19:38 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-06 10:13 backport requests for 4.x-testing Jan Beulich
2012-03-06 10:38 ` Keir Fraser
2012-03-06 11:04 ` Andrew Cooper
2012-03-07  7:25   ` Roderick Colenbrander
2012-03-07  9:43     ` Keir Fraser
2012-03-13 16:50     ` Ian Jackson
2012-03-13 17:25       ` Teck Choon Giam
2012-03-13 17:52         ` Teck Choon Giam
2012-03-13 18:23           ` Teck Choon Giam
2012-03-14 10:03             ` Ian Jackson
2012-03-14  9:58           ` Ian Jackson
2012-03-14 11:37         ` Ian Jackson
2012-03-14 23:08           ` Teck Choon Giam
2012-03-19 14:22             ` Teck Choon Giam
2012-04-03 15:04               ` Ian Jackson
2012-03-07  9:43   ` Keir Fraser
2012-03-07 10:44     ` Andrew Cooper
2012-03-07 10:59       ` Keir Fraser
2012-03-07 11:06         ` Jan Beulich
2012-03-07 11:08           ` Andrew Cooper
2012-03-07 19:38       ` Ian Campbell [this message]
2012-03-08 10:38         ` Andrew Cooper
2012-03-08 10:42           ` Keir Fraser
2012-03-13 16:52     ` Ian Jackson
2012-03-24 17:27   ` Konrad Rzeszutek Wilk
2012-03-29  9:22     ` Keir Fraser
2012-03-29 11:32       ` Teck Choon Giam
2012-03-29 11:42         ` Teck Choon Giam
2012-03-29 15:11         ` Konrad Rzeszutek Wilk
2012-03-29 15:26           ` Teck Choon Giam
2012-03-29 15:56             ` Konrad Rzeszutek Wilk
2012-03-29 16:20               ` Teck Choon Giam
2012-03-29 16:23                 ` Konrad Rzeszutek Wilk
2012-03-29 16:39                   ` Teck Choon Giam
2012-03-29 11:55     ` Stefano Stabellini
2012-03-29 15:31       ` Jan Beulich
2012-03-29 17:06         ` Stefano Stabellini
2012-03-30  8:23           ` Keir Fraser
2012-03-30  9:59             ` Stefano Stabellini
2012-04-03 15:08     ` Ian Jackson
2012-04-03 15:15       ` Teck Choon Giam
2012-04-03 16:58         ` Ian Jackson
2012-04-03 19:50           ` Teck Choon Giam
2012-04-03 20:02             ` Teck Choon Giam
2012-04-04 10:22               ` Ian Jackson
2012-04-04 12:54                 ` Teck Choon Giam
2012-04-04 15:09                   ` Ian Jackson
2012-03-07  9:18 ` Keir Fraser
2012-03-07 10:10   ` Jan Beulich
2012-03-08 10:00   ` Jan Beulich
2012-03-08 10:05     ` Keir Fraser
2012-03-08 10:45   ` Jan Beulich
2012-03-08 11:00     ` Keir Fraser
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=1331149122.14355.4.camel@cthulhu.hellion.org.uk \
    --to=ian.campbell@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=keir@xen.org \
    --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).