Re: Constructing trees from several repositories

[HMahaffey]

In a message dated 9/29/00 6:08:26 PM Eastern Daylight Time, 
address@hidden writes:


> address@hidden writes:
> > 
> > I was a bit disappointed when I ran the initial checkout again like I did 
> > when I first created the tree.  It worked fine until it would enter a 
> > directory from a different repository, say repos2, and would complain 
> that 
> > the module I was checking out didn't exist in repos2 (which was true).
> 
> I'm confused -- why are you trying to run checkout on a tree that's
> already checked out?  As you say, update works correctly, and that's
> what you should be using, not checkout.  It would be nice if checkout
> in a cvs-controlled directory worked exactly like update -d, but it
> doesn't and it would be very difficult to fix it.
> 
Ok, you're right, that was dumb.  :)  The biggest problem from mixing the 
trees came from something similar to what I described in my next note, where 
a "cvs tag" at the top of the tree would abort if I didn't have write access 
(which I don't) to any one of the other repositories that I checked-out from. 

Hmmm... perhaps that's all if it after all: can "tag" be told to ignore 
directories I don't have write-access to?

Thanks for the response!

:)hal mahaffey