ot; [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
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 tempo
inal Message -
From: "Francis Irving" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
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 "
-l parent (To avoid my default "co -P")
Copy the "new" folder into the local "parent" dir
cd parent
cvs add new
etc.
It *would* be nice to have a "add --new" or something
like that (there must be some single-letter option we
can use). I think the only t
: Noel L Yap)
Subject: cvs add --new
I like Rex's idea of creating a new way to add
a new directory (and contents) to the repo.
I do this all the time; "Import" is typically not
what I want to do, and I haven't yet written a
wrapper script to perform this sequence of actions
so I en
On Thu, Feb 15, 2001 at 12:28:18PM -0500, Mr. Aldo D. Longhi wrote:
I like Rex's idea of creating a new way to add
a new directory (and contents) to the repo.
I do this all the time; "Import" is typically not
what I want to do, and I haven't yet written a
wrapper script to perform this
Mike Castle wrote:
On Thu, Feb 15, 2001 at 12:28:18PM -0500, Mr. Aldo D. Longhi wrote:
I like Rex's idea of creating a new way to add
a new directory (and contents) to the repo.
I do this all the time; "Import" is typically not
what I want to do, and I haven't yet written a
wrapper script to
My main problem with "Import" is that it does not insert
all the metadata into my existing directory structure.
So once I import the stuff, I then have to move it out
of the way (rename the dir) and check everything out
again. "Add" takes care of this for me.
It seems that what is
On Thu, Feb 15, 2001 at 01:43:32PM -0600, [EMAIL PROTECTED] wrote:
["cvs add --new" wanted because "cvs import" doesn't insert metadata]
It seems that what is being asked for is a CVS command to convert a
regular directory into a cvs workspace directory so that it isn
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
