FAQWhat's the best way to constantly follow this tree? Just set up linux-next as a remote on any existing clone of Linus' tree and the "fetch" will forcibly update the linux-next/master branch (remember to not have that branch checked out when you fetch). If you keep a continuing git tree for this, you will have the history of all the next trees because Stephen tags each one. ... $ git remote add linux-next git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git $ git fetch linux-next $ git fetch --tags linux-next ... # later on $ git remote update ... When and how will linux-next get into linus tree? I'll cite a email between Paolo Ciarrocchi and Stephen Rothwell to answer this: > Is Linus going to pull from that tree as soon as we reach -rc0 or this > is just a tree > used for testing what will be pushed to Linus as soon as the two weeks > merge window > open? The intention is the latter. I hope to help people sort out some of the conflicts and cross subsystem issues before we get into the merge window and the code gets into Linus' tree. Andrew Morton also hopes that the linux-next tree may get more testing that the -mm tree did if we can stop it having to many regressions by only including the less experimental code that is destined for the next kernel release. How can i help? Please test the current linux-next tree as good as possible and report problems to the mailinglist, the subsystem/driver maintainers or http://bugzilla.kernel.org/. |