[Top][All Lists]

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

Re: cvs add --new

From: Eric Siegerman
Subject: Re: cvs add --new
Date: Thu, 15 Feb 2001 16:30:34 -0500
User-agent: Mutt/1.2.5i

On Thu, Feb 15, 2001 at 01:43:32PM -0600, address@hidden 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't 
> necessary to do an initial checkout. But in virtually every situation 
> (there may be an occasional exception), everyone that is working on a 
> project needs their own workspace directory.  So, everybody for the most 
> part has to do a checkout anyway.

If it's a one-person project (including local mods to downloaded
open-source code), the savings would be rather greater -- nearly
50% of the effort of CVSifying a package.

I also resented at first that I had to go through this extra
step.  But I came to appreciate it:
  - It's comforting to know that "import" is a read-only
    operation as far as the original directory is concerned; you
    don't have to back it up first
  - It's possible to diff the original directory with the new
    sandbox to make sure nothing went wrong with the import

The one thing that would be useful, IMO, would be a way to create
a top-level directory in the repository.  The trick of doing a
"-l" checkout of the root directory is a kludge.


|  | /\
|-_|/  >   Eric Siegerman, Toronto, Ont.        address@hidden
|  |  /
Interviewer: You've been looking at the stars all your life:
Is there anything in astrology?
Arthur C. Clarke: It's utter nonsense.  But I'm a Sagittarius,
so I'm naturally skeptical.

reply via email to

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