info-cvs
[Top][All Lists]
Advanced

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

Re: cvs add --new


From: Dennis Jones
Subject: Re: cvs add --new
Date: Fri, 16 Feb 2001 13:55:29 -0800

Far be it from me to suggest a method or mechanism for HOW it should be
implemented, I only wanted to echo the desire for a more intuitive way to
add new projects to the repository.

- Dennis

----- Original Message -----
From: "Noel L Yap" <address@hidden>
To: <address@hidden>
Cc: <address@hidden>
Sent: Friday, February 16, 2001 1:39 PM
Subject: Re: cvs add --new


> The problem with overloading "cvs add" to create new modules is that one
of "cvs
> add"'s preconditions is that the module already exists.  I can understand
> requests like having "cvs add -r" to recursively add down a directory
hierarchy,
> or "cvs add -p" to recursively add up a directory hierarchy, but I can't
see
> "cvs add" being overloaded to mean import a new module (unless, of course,
you
> have a workspace that was created with "cd ~/root; cvs co .", then you
want to
> do a "cd ~/.root; md newmodule; cvs add -r newmodule").
>
> Noel
>
>
>
>
> address@hidden on 2001.02.16 13:26:34
> If we are signing a petition here, you can put me on it too.  I really
> dislike having to use import at all, whether for new modules, or even for
> vendor branhces.
>
> While most people have said they don't want to complain, or be critical
> about CVS's lack of support in this area, I will be honest and admit that
I
> think this is something worth being critical about.  Unlike most CVS
> functionality, using import to create a new module is a nuisance,
> unintuitive, and error prone.  No question about it -- it should be
changed.
>
> - Dennis
>
> ----- Original Message -----
> From: "Francis Irving" <address@hidden>
> To: <address@hidden>
> Sent: Friday, February 16, 2001 2:50 AM
> Subject: Re: cvs add --new
>
>
> 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.
>
>
> _______________________________________________
> Info-cvs mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/info-cvs
>
>
> _______________________________________________
> Info-cvs mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/info-cvs
>
>
>
>
>
> This communication is for informational purposes only.  It is not intended
as
> an offer or solicitation for the purchase or sale of any financial
instrument
> or as an official confirmation of any transaction. All market prices, data
> and other information are not warranted as to completeness or accuracy and
> are subject to change without notice. Any comments or statements made
herein
> do not necessarily reflect those of J.P. Morgan Chase & Co. Incorporated,
its
> subsidiaries and affiliates.
>




reply via email to

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