Re: Kernel SCM: When does CVS fall down where it REALLY matters?

[Pavel Machek]

Hi!

> I am considering adding some enhancements to CVS to address deficiencies 
> which adversely affect my productivity.  Since it would obviously be 
> nice to have a completely free (or even GPL :-) tool which is not 
> considered to consist of unacceptable compromises in the process of 
> kernel development I would like to know what the Bitkeeper users 
> consider the minimum acceptable set of improvements that CVS would 
> require for broader acceptance.  Obviously the tremendous set of 
> features that Bitkeeper has are nice, but I'd like to narrow the 
> comparative flaws to a manageable set.

My pet feature?

cvs dontcommit file.c

What it should do? Mark changes in file.c as private to me, so that it
never tries to commit them to official tree. It would be best if cvs
diff just pretended changes are not there.

So, if I checkout tree, do some dirty hacks to make it compile, do cvs
dontcommit ., cvs diff should show nothing and cvs commit should try
to commit nothing. That would be nice,
									Pavel
-- 
(about SSSCA) "I don't say this lightly.  However, I really think that the U.S.
no longer is classifiable as a democracy, but rather as a plutocracy." --hpa