public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
* linux-next: tip tree question
@ 2009-10-12  3:56 Stephen Rothwell
  2009-10-12  6:49 ` Ingo Molnar
  0 siblings, 1 reply; 3+ messages in thread
From: Stephen Rothwell @ 2009-10-12  3:56 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: linux-next, LKML

[-- Attachment #1: Type: text/plain, Size: 760 bytes --]

Hi all,

I noticed that the auto-latest branch of the tip tree (which is what is
included in linux-next) has had the tip out-of-tree branch merged into
it.  This seems to just introduce lots of commits into linux-next that
have nothing to do with the tip tree (some of which contain fixes that
are also in Linus' tree) and adds a localversion-tip file.

I was wondering if this was done out of necessity or by oversight.

I have reverted commit e67d8da85f7a4c2772fe3731de9396b6d01a045e ("Merge
branch 'out-of-tree' into auto-latest") from linux-next for today and the
x86_64 allmodconfig and powerpc ppc64_defconfig builds still seem OK.

-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2009-10-12  8:43 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-10-12  3:56 linux-next: tip tree question Stephen Rothwell
2009-10-12  6:49 ` Ingo Molnar
2009-10-12  8:42   ` Stephen Rothwell

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox