linux-next

git tree URL:
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git

Testbuild status

On http://kisskb.ellerman.id.au/kisskb/branch/9/ you can currently see the status of each testbuild Stephen and his team did.

linux-next specials

The trees master branch will rebase on an almost daily basis (maybe slower at the start).

It consists of subsystem git an quilt trees. The merge log is in its Next/merge.log file
and Next/quilt-import.log accordingly the imports log of the quilt trees.
In Next/Trees you can find an onverview of the currently included trees (see also Included trees).

Between each merge the tree was built with allmodconfig for x86_64 and powerpc
(by Stephen Rothwell only currently).

The tree is also tagged with a pattern next-YYYYMMDD while the current tag is
also used for the kernel version (via the localversion-next file machanism).

Included trees

Always up to date link: http://git.kernel.org/?p=linux/kernel/git/sfr/linux-next.git;a=blob;f=Next/Trees;hb=HEAD
State from 2008-02-19:
Trees included into this release:

Name            Type    URL
----            ----    ---
origin          git     git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
driver-core     quilt   http://kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-01-driver/
pci             quilt   http://kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-02-pci/
usb             quilt   http://kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-03-usb/
device-mapper   quilt   http://www.kernel.org/pub/linux/kernel/people/agk/patches/2.6/editing/
hid             git     git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git
i2c             quilt   http://khali.linux-fr.org/devel/linux-2.6/jdelvare-i2c/
kernel-doc      quilt   http://oss.oracle.com/~rdunlap/kernel-doc-patches/current/
avr32           git     git://git.kernel.org/pub/scm/linux/kernel/git/hskinnemoen/avr32-2.6.git
v4l-dvb         git     ssh://master.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-next.git
s390            git     git://git390.osdl.marist.edu/pub/scm/linux-2.6.git
sh              git     ssh://master.kernel.org/pub/scm/linux/kernel/git/lethal/sh-2.6.git
jfs             git     git://git.kernel.org/pub/scm/linux/kernel/git/shaggy/jfs-2.6.git
kbuild          git     git://git.kernel.org/pub/scm/linux/kernel/git/sam/kbuild.git
pata            quilt   http://kernel.org/pub/linux/kernel/people/bart/pata-2.6/patches/
libata          git     git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
nfs             git     git://git.linux-nfs.org/projects/trondmy/nfs-2.6.git
xfs             git     git://oss.sgi.com:8090/xfs/xfs-2.6.git
infiniband      git     git://git.kernel.org/pub/scm/linux/kernel/git/roland/infiniband.git
acpi            git     git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6
blackfin        git     git://git.kernel.org/pub/scm/linux/kernel/git/cooloney/blackfin-2.6.git
nfsd            git     git://git.linux-nfs.org/~bfields/linux.git
firewire        git     git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394-2.6.git
hwmon           git     git://lm-sensors.org/kernel/mhoffman/hwmon-2.6.git

About

In short the linux-next git tree is the merge of all of the developer and maintainers trees, much like the -mm tree is today. There are some automated buildtest and maintainers get notification on merge and buildproblems. For a more detailed explanation please have a look at the initial announcement of linux-next.

Mailinglist

On vger.kernel.org there is a corresponding mailinglist for linux-next.
You can e.g. subscribe via this link.
An archive of the mailinglist is kept here: http://marc.info/?l=linux-next

Initial announcement

The initial announcement of linux-next from Stephen Rothwell:
http://marc.info/?l=linux-next&m=120277814924607&w=4
and this is a minor addition of him noting the other brave guys that stood up for this job:
http://marc.info/?l=linux-next&m=120278315530542&w=4

Disclaimer: this summary page for linux-next (by Frank Seidel) may be totally bogus or misleading. Use at own risk.
Author contact: fseidel@suse.de or frank@f-seidel.de
Last updated: 2008-02-18