From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Alex Sharp <alex.sharp@orionvm.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH] Fix various format string mismatches.
Date: Thu, 31 Oct 2013 18:19:20 +0000 [thread overview]
Message-ID: <52729F28.2020805@citrix.com> (raw)
In-Reply-To: <A4D3962C02EE81408CC4341DF532AAC3364670@Exchange2.orionvm.com>
On 31/10/13 18:14, Alex Sharp wrote:
> Just to double check, am I basing this patch off branch staging on git://xenbits.xen.org/xen.git ? (Last commit 1e2bf05ec37cf04b0e01585eae524509179f165e) or branch staging-4.3?
All development happens against staging, even work like this.
It will then be backported by a stable tree maintainer. Strictly
speaking the maintainer gets final say on whether something justifies
backporting (subject to persuasive arguments one way or another), but
this hopefully uncontentious and obviously a GoodThing.
~Andrew
next prev parent reply other threads:[~2013-10-31 18:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 17:57 [PATCH] Fix various format string mismatches Alex Sharp
2013-10-31 18:01 ` Andrew Cooper
2013-10-31 18:05 ` Andrew Cooper
2013-10-31 18:14 ` Alex Sharp
2013-10-31 18:19 ` Andrew Cooper [this message]
2013-11-19 12:27 ` 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=52729F28.2020805@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=alex.sharp@orionvm.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.