[Top][All Lists]

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

Re: Vendor software update and branches

From: Mark
Subject: Re: Vendor software update and branches
Date: 17 Jan 2006 18:56:45 -0800
User-agent: G2/0.2

I've been doing more testing and see that by useing the -b 1.1.2
argument for my new import, the new vendor code is not generally seen
on the main trunk.  Main continues to look at 1.1.1 and I can deal with
the merges in another branch.   (exactly what I need)

After the import I get a message suggesting that I run "cvs co -jTAG
-jTAG" and check in.  However I see that this is just merging the code
into the main trunk, so I believe I can hold off on that.

The last problem I can see at this point is that new files from the new
import immediately show up on the main trunk (probably because there is
no 1.1.1, so it defaults to viewing  1.1.2).

I believe, this is why you suggested using cvs version 1.12.13 'cvs
import -X'.

But how risky is it to upgrade from 1.11 to 1.12 ??


reply via email to

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