[linux-dvb] [ANNOUNCE] v4l-dvb development migrating from CVS to Mercurial

Adrian Bunk bunk at stusta.de
Fri Feb 3 18:23:19 CET 2006


On Fri, Feb 03, 2006 at 04:59:45PM +0100, Klaus Schmidinger wrote:
> 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?
>...

What exactly is the problem with using Mercurial?

It's GPL'ed and not that hard to use.

> Klaus

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed




More information about the linux-dvb mailing list