> >I did consider the possibility of allowing "cvs co new-dir" to just
> >create a new directory regardless of whether there's a modules entry
> >with the name "new-dir" yet or not.  However I do feel rather strongly
> >that the use of the modules feature should be encouraged as much as
> >possible.
> 
> I think either CVS should require CVSROOT/modules or it shouldn't.  Your
> proposal is an "in between" decision that could confuse people.  The way I would
> go about it would be to have "cvs co module" require that module exist in
> CVSROOT/modules.  I know this would probably break many people's use of "cvs
> co", but I don't think it's too difficult to add appropriate lines in
> CVSROOT/modules.

Make sure that you don't permit 'cvs co mispelling' to create a new
directory when 'cvs co misspelling' was intended.

How about 'cvs new module-name module-dir local-dir' to create a new
entry, and update the module file all in one? ('local-dir' might be '.').

Reply via email to