From: Michael Neuling <mikey@neuling.org>
To: Greg KH <gregkh@suse.de>
Cc: michael@ellerman.id.au, linux-kernel@vger.kernel.org
Subject: Re: git tree for testing stable kernels RCs
Date: Thu, 05 Aug 2010 11:42:21 +1000 [thread overview]
Message-ID: <7065.1280972541@neuling.org> (raw)
In-Reply-To: <20100804145025.GA21125@suse.de>
In message <20100804145025.GA21125@suse.de> you wrote:
> On Wed, Aug 04, 2010 at 11:05:04AM +1000, Michael Neuling wrote:
> > Greg,
> >
> > Do you have a git tree with RC candidates for the stable kernels? I'm
> > interested in full trees, not just the patch series like you have in
> > your stable-queue.git tree. I'm happy if this tree is re-based before
> > the final stable release.
>
> Nope, I don't, the workflow for the stable trees does not lend itself to
> a git tree that doesn't constantly change, sorry.
No problem, I thought I'd ask anyway.
> > The reason I ask is that Michael Ellerman has added the stable kernels
> > to his list of trees he tests with his kisskb infrastructure. You can
> > see the results here:
> >
> > stable-2.6.27: http://kisskb.ellerman.id.au/kisskb/branch/19/
> > stable-2.6.32: http://kisskb.ellerman.id.au/kisskb/branch/17/
> > stable-2.6.34: http://kisskb.ellerman.id.au/kisskb/branch/15/
> > stable-2.6.35: http://kisskb.ellerman.id.au/kisskb/branch/16/
> >
> > These results have already helped us find bugs but it would be even
> > better if we could fix the problems before the final release.
>
> Just simple build bugs, right? Not that it's not nice to catch them
> though.
Yes, just build bugs. They seem to happen from time to time with
stable.
> > If you don't have this available we're likely to build one but before
> > we do, I thought I'd ask if you had this pre-built somewhere anyway.
>
> Nope, have fun building it :)
Fun git party time, woot!! :-)
Mikey
prev parent reply other threads:[~2010-08-05 1:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 1:05 git tree for testing stable kernels RCs Michael Neuling
2010-08-04 14:50 ` Greg KH
2010-08-05 1:42 ` Michael Neuling [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=7065.1280972541@neuling.org \
--to=mikey@neuling.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@ellerman.id.au \
/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.