From: David Vrabel <david.vrabel@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Keir Fraser <keir@xen.org>, Jan Beulich <JBeulich@suse.com>
Subject: Re: [xen-unstable test] 18784: regressions - trouble: broken/fail/pass
Date: Wed, 28 Aug 2013 16:33:02 +0100 [thread overview]
Message-ID: <521E182E.1050707@citrix.com> (raw)
In-Reply-To: <21022.5685.589289.319751@mariner.uk.xensource.com>
On 28/08/13 16:24, Ian Jackson wrote:
> Jan Beulich writes ("Re: [Xen-devel] [xen-unstable test] 18784: regressions - trouble: broken/fail/pass"):
>> On 28.08.13 at 17:05, Ian Jackson <Ian.Jackson@eu.citrix.com> wrote:
>>> If you point me at something else to use as input to the push gate I
>>> would be happy to use that.
>>
>> I guess the kernel maintainers are in a better position to point out
>> the most stable tree/branch to follow for that purpose.
>
> Is there a single branch or tag that always corresponds to the
> "current stable kernel" ? Or do we have to update this every n months ?
No. Each stable series has its own branch.
I would recommend using the 3.10.y stable tree which is the current
longterm stable tree.
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
branch: linux-3.10.y
David
next prev parent reply other threads:[~2013-08-28 15:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 8:17 [xen-unstable test] 18784: regressions - trouble: broken/fail/pass xen.org
2013-08-28 9:00 ` Jan Beulich
2013-08-28 14:10 ` Jan Beulich
2013-08-28 15:05 ` Ian Jackson
2013-08-28 15:12 ` Ian Campbell
2013-08-28 15:15 ` Ian Jackson
2013-08-28 15:21 ` Jan Beulich
2013-08-28 15:24 ` Ian Jackson
2013-08-28 15:33 ` David Vrabel [this message]
2013-08-28 15:53 ` Ian Jackson
2013-08-28 15:38 ` Jan Beulich
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=521E182E.1050707@citrix.com \
--to=david.vrabel@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=keir@xen.org \
--cc=xen-devel@lists.xenproject.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.