[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: "cvs commit" features

From: Mike Ayers
Subject: Re: "cvs commit" features
Date: Wed, 09 Oct 2002 11:48:10 -0700
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826

Reinstein, Shlomo wrote:

Of course, a user can always use "cvs add" and "cvs remove" to add or remove
files, but these two options can help him/her make sure they didn't forget
to do this for some of the files.

This is one of those things that might work really well, but only for certain development models. For instance, I am using a GUI based tool. It likes to create lots of files that may or may not need to be archived. I have experimentally determined that if I archive a certain set of them, then there seems to be no problems. Do I want CVS to pester me about the ones I'm not archiving every time I do a commit in that directory? No way!

And just think what would happen if you inadvertently did your CVS commit without making clean first...

        Nannyware sucks.

Optional nannying? Hmmm - doesn't the nannyware model *require* that the nagging not be optional?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]