A recent announce at LKML introduced a new concept of integrated development
between the several subsystem trees, called linux-next.
The basic idea is to have a common tree that merges all development efforts,
helping to solve merge conflicts before arising at Linus main tree. More
details can be seen at the original announce [1].
With this concept, what happens is that a new patch will mature at the
development branches and at linux-next. At the release of a new kernel (let's
say 2.6.25), a merge window will open to the next kernel (2.6.26). The patches
for the next kernel will be submitted by each subsystem maintainer. Since those
patches were already tested on linux-next tree, the merging process will
become easier and the newer kernel will become more stable.
So, linux-next contains the patches for 2.6.25, plus the patches expected to be
added at kernel 2.6.26.
For this to happen, I've created a newer -git tree, containing the committed
changesets that are expected to appear at the next kernel. It contains
basically the same patches already present on -hg and v4l-dvb.git trees, plus
the base patches from linux-next (at 'stable' branch). Another branch
('master') will contain also the merged patches from the other subsystems.
For those brave enough to test it, the tree is available at [2]. Please be
warned to use this on a testing system, since patches at core subsystems
(ext2, vfs, etc) may be broken there.
In order have a single point where all trees are listed, I've updated
README.patches file, and the main tree at http://linuxtv.org/hg with the newer
tree. I've also added a link to README.patches there.
[1] http://lkml.org/lkml/2008/2/11/512
[2] http://www.kernel.org/git/?p=linux/kernel/git/mchehab/linux-next.git;a=summary
Cheers,
Mauro
_______________________________________________
linux-dvb mailing list
linux-dvb@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
