Re: cvs add --new

[Francis Irving]

For TortoiseCVS (an Explorer extension interface to CVS), I felt
forced to implement exactly this feature via a kludge using "cvs
import".

(It makes an empty directory in a temporary place, and does cvs import
on that, then checks it out again, and copies the CVS bit to the
working directory).

New users expect to just be able to go:
        cvs add --newmodule mynewmodule
and make that as a new module, already checked out in place.

Most everything else in cvs is easy to explain to people.

I'm not being critical that this isn't there, just giving my support
to folk who would like this feature!

Francis

On Thu, 15 Feb 2001 14:01:56 -0800, address@hidden wrote:

>Actually I comment was meant to point out a percieved flaw in CVS.  When I show
>developers CVS in the environment that I work, putting new projects into CVS is
>always
>a place that they see weakness in CVS as they either have to pretend they are
>their
>own vendor, or use the top level dir checkout trick.  I was simply suggesting
>that we
>can improve the image of CVS by adding an easy way for a user to create a new
>top
>level directory for a new subsystem.
>
>Rex.