Re: how to?

[Ian Molton]

On Mon,  3 Sep 2001 14:39:04 -0400 (EDT)
address@hidden (Greg A. Woods) scribbled insanely:

> Don't try to use regular branches in a vendor-branched module.  It
> doesn't work well, and indeed wasn't really intended to work.
> 
> There can only ever really be one successful vendor branch too, despite
> what some of the documentation might lead you to believe, and especially
> contrary to what the original "CVS-II" paper suggests.
> 
> If you really need to have local branches *and* a vendor branch then
> you'd be much better off using "cvs add" to create and populate your
> module and then to create a real branch on which you manually add the
> vendor code to.  Don't use "cvs import" at all, ever, for this kind of
> thing.

Sorry, but could you slow down a touch?

whats a 'vendor branched module' ?

surely this is equivalent to me making my own program, branching it, and
then going back and modifying the 'trunk'? (is trunk the right term?).

All I want to do is keep the linux kernel in local CVS so I can make
branches for the arm patches, and make branches off those branches for my
own modifications. Is this not possible?