ECTED]>
Cc: <[EMAIL PROTECTED]>
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
ennis
- Original 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
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 "cvs
import".
(It makes an
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).
N
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 checkou
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 di
>
> 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
On Thu, Feb 15, 2001 at 01:37:00PM -0500, Mr. Aldo D. Longhi wrote:
> Mike Castle wrote:
> >I still can't see what the problem with import is.
>
> 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
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
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 s
(bcc: 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 act
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 end up doing it manually:
cvs -F co -l (To avoid my
12 matches
Mail list logo
