Re: importing vendor branches

[Greg A. Woods]

[ On , May 4, 2001 at 12:22:16 (-0400), Laine Stump wrote: ]
> Subject: Re: importing vendor branches
>
> Another way to "fix" this is to just force a "null commit" (new
> revision, but 0 lines changed) on the trunk of each new file right
> after it is initially imported.

That works too, but potentially makes merges a lot more work....

I still don't see the problem here.  If everyone who might do a checkout
reads at least the subject lines of the mail from loginfo they'll know
when an import was done, and in what module, and be able to avoid doing
a fresh checkout that might result in an inconsistent working directory.

It's not as if the problem is created by "cvs import" -- it's created by
the unsuspecting person doing the "cvs co".  The fix isn't to break "cvs
import", or to break the vendor-branch feature (eg. by doing a null
commit"), but rather to improve team communications to the point where
nobody will get caught in this situation.  (And of course to make sure
everyone uderstands when *not* to use "cvs import" in the first place! :-)

-- 
                                                        Greg A. Woods

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