lkml.org 
[lkml]   [2008]   [Nov]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: linux-m68k.git
Hi Geert,

On Wed, 19 Nov 2008 09:44:03 +0100 (CET) Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>
> What's the purpose of your m68k-current tree? There should not be anything
> in m68k#for-linus that's not in m68k#for-next.

I have a set of trees (15 so far) that are just patches pending for the
current release (mostly bug fixes). These trees are usually empty (since
things get sent to Linus fairly quickly during the -rc's) but it means
that between the time between when the fixes are ready and when Linus
integrates them, people testing linux-next don't have to worry about bugs
that already have fixes.

Having them in a (logically) separate tree, as far as linux-next is
concerned, means that if I have to drop your -next tree for any reason
then the bug fixes can stay.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[unhandled content-type:application/pgp-signature]
\
 
 \ /
  Last update: 2008-11-19 10:31    [W:0.040 / U:0.720 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site