Re: help, doing a CVS import messed up my working dir!?!?!

[Mark D. Baushke]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dave Korn <address@hidden> writes:

> > The script Chris provided in the URL I gave you avoids this by making
> > version 1.2 always dead. This means you will explicitly need to move
> > what you want from the VENDOR branch into the main trunk rather than
> > implicitly (and is also what the 'cvs import -X' does).
> 
> > If you are going to add a patch, pick up the -X feature to cvs import
> > that is in the thread I gave previously. It is an easier to audit
> > reality and allows for someone who comes after you to be able to do the
> > right thing.
> 
>   I'm not sure; isn't what I want for my purposes just a quick hack to the
> server so that the "branch 1.1.1" directive is just never ever added to the
> RCS file by an import (subject to a commandline option being specified)?

I could be mistaken, but I think you will not like the results of such
an action... you still need to worry about removed files from one import
to another and finding them will be 'work' depending on how you hack
cvs.

> Couldn't I just let the r1.1 that you mentioned that was a copy of r1.1.1.1
> be the base of the main trunk?

A quick hack fork of the cvs sources means that only you will be able to
answer questions about interactions of the various commands. I suspect
you will find this to be a lot more painful than you would ever imagine
right now as you move forward over time.

        -- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQFDCh7kCg7APGsDnFERAiynAKDrtDd7c4HEgc5oPZE788RDHYE/yQCcDx0P
dd7peoP6BSS9sU78u22A9zc=
=Eb+X
-----END PGP SIGNATURE-----