Re: Problem with importing third-party sources and adding/committing changes

[Greg A. Woods]

[ On Sunday, November 14, 2004 at 14:09:35 (-0800), Mark D. Baushke wrote: ]
> Subject: Re: Problem with importing third-party sources and adding/committing 
> changes 
>
> Again, this is being addressed by the 'cvs import -X' option which
> creates a dead version 1.2 on initial import.

Indeed, but as I've said before I don't think that's really going to
solve the problem -- it's a poor hack on a bad hack.

What "cvs import" really needs is the ability to import to the trunk
and/or to any other "normal" CVS branch.  I added such a feature to CVS
a long time ago but my changes did not survive.

Alternately, or additionally, my old "cvs add" proposal needs to be
implemented.

The real underlying benefit most users seem to find in "cvs import" is
that it's simply easier to use than "cvs add" and "cvs commit" over a
whole tree, especially when new directories are being created.  My "cvs
add" proposal fixes that problem in the most clean and elegant and
complete way possible.

Once it's easier to avoid the old magic CVS vendor branch then people
might not be so reluctant to commit vendor releases to a normal branch
and to learn to do merges of vendor changes to local branches in the
normal way they would merge any changes between branches.

-- 
                                                Greg A. Woods

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