Mauro Carvalho Chehab wrote: > Dear V4L/DVB guys, > > We are proud to announce that we are doing some important steps to > improve v4l/dvb development. Currently, the projects use a very old SCM > (Source Configuration Management), based on RCS files (CVS). > > Although it was good in the past, now newer concepts were introduced to > SCM that allows better models of development. It brings several > advantages over CVS like: > > 1) Capable of being decentralized. Each developer may have its own > local copy, with local commits; > 2) Atomic commits. on rcs based systems, you have a separate control > for each file, not for the patchset. On newer SCMs, the patchset is > stored as an unique unit; > 3) Better handling for conflict resolution; > 4) Commit undo > > And others. For a better description of Mercurial, you should look at > http://www.selenic.com/mercurial/. They have also an IRC channel on > freenode (#mercurial). I've never heard of Mercurial. CVS worked fine for me, and I'm not going to use Mercurial. So, this pretty much cuts me off of the driver CVS then, doesn't it? Will there be a "mirror CVS" that can be used to just check out the latest version, or at least nightly snapshots of the complete driver source? Klaus
