Re: Strategy for tracking 3rd party source.

[Sergei Organov]

address@hidden writes:
> I need to track some 3rd party source code,
[...]
> What I am thinking of doing is reserving HEAD for the 3rd party source
> and then making a branch, MYBRANCH.  The other projects can then pull
> from MYBRANCH (our internal HEAD so to speak), I can then do the
> import, merge the changes into MYBRANCH and commit the working code
> into MYBRANCH after its working.  That way MYBRANCH is always usable.
> 
> Is this a reasonable approach?  Is there a better way?

The approach is reasonable, but long-standing active branches are not
where CVS does a very good job. The longer the branch is the slower the
checkout/update on the branch will be. Provided you are working with
Linux kernel, this may hurt you very quickly.

For better ways refer to other responses you've got.

-- 
Sergei.