lkml.org 
[lkml]   [2011]   [Aug]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Future of the -longterm kernel releases (i.e. how we pick them).
On Wed, Aug 24, 2011 at 09:49:22PM -0700, Brian Swetland wrote:
> On Tue, Aug 23, 2011 at 9:57 PM, Greg KH <greg@kroah.com> wrote:
> > On Wed, Aug 17, 2011 at 10:33:05AM -0700, Brian Swetland wrote:
> >> As far as long-term kernels goes, from the Android perspective we
> >> strongly prefer to snap up to the most recent released kernel on every
> >> platform/device release.  I prefer to be as up to date on bugfixes and
> >> features from mainline as possible and minimize the deltas on our
> >> stack 'o patches as much as possible.
> >
> > That's good to hear.
> >
> >> We've been getting more aggressive about merging in the -rc#s and then
> >> rebasing on the final during development (before final stabilization
> >> freeze for a release) in the last year or so, and it seems to work
> >> pretty well.
> >
> > Is your kernel git tree public during this merge cycle so that others
> > can track it?  I tried to dig through android.kernel.org but there are a
> > lot of different kernel trees there :(
>
> We really need a "which branch is which" quick guide that's easily
> findable. kernel/common is always where our generic patch stack
> lives, and it looks like android-3.0 is the most recent (which has
> 3.0.1 merged in).
>
> http://android.git.kernel.org/?p=kernel/common.git;a=summary

Thanks for the pointer.

If you ever get such a quick guide, I'd appreciate a link to it.

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2011-08-26 02:07    [W:0.103 / U:0.444 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site