[Top][All Lists]

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

Re: CVS - import to 1.1

From: Greg A. Woods
Subject: Re: CVS - import to 1.1
Date: Mon, 11 Mar 2002 23:26:20 -0500 (EST)

[ On Monday, March 11, 2002 at 21:22:44 (-0500), Matthew Persico wrote: ]
> Subject: CVS - import to 1.1
> I am in the middle of getting a group of developers to convert to CVS. They
> have all been raised on SCCS, PVCS, so I have to go slow with the whole
> concept of sandboxing and lockless checkouts. So slowly, in fact, that they
> are actually going to start out using cvs admin -l.  Sigh.

I've never seen or heard of this working well enough in practice to be
of any use whatsoever.

Just get them to dive right in.  There is lots of water in the pool --
they will not bang their heads on the bottom.  The sooner you get them
wet the better.

If they're too opposed to working together and using concurrent edits
and merging then why use CVS in the first place?  There are (many)

> What I'd like to know is this:
> Is there a way to cvs import into 1.1, not

Nope.  I made some hacks to CVS to do that once upon a time, but those
were in the days long before RCS support was integrated and my changes
will no longer apply to the code.  I'm not so sure I think that's the
right direction to go in any more anyway.  I believe for a great number
of reasons that using "cvs add" is the correct approach, even for the
initial creation of a new project that starts from an existing
collection of files.

> Without the branch, the
> first lock and commit attempts will work as advertised.

hmmm.... maybe....

> If I cannot do this, then I have to create an empty project and then write a
> script that will recurse a tree of code, doing cvs adds as appropriate and
> I'd rather not do that.

What's so hard about that?  I know it would be nice to have such support
-- so well that I even wrote a full in-depth proposal for it -- but in
the mean time, and especially for the initial creation of projects, a
wee tiny script that is simple enough to write once directly on the
command line should not be a problem.

                                                                Greg A. Woods

+1 416 218-0098;  <address@hidden>;  <address@hidden>;  <address@hidden>
Planix, Inc. <address@hidden>; VE3TCP; Secrets of the Weird <address@hidden>

reply via email to

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