[parisc-linux] CVSy stuff

[James Bottomley]

On Tue, 2003-03-18 at 09:33, Matthew Wilcox wrote:
> So how about this model...
> 
> 1. -> linus
> 1.1 -> LINUS_260
> 1.2 -> LINUS_261
> 1.2.1 -> parisc_261
> 1.2.1.1 -> CVS261_PA1
> 1.2.1.2 -> CVS261_PA2
> ...
> 1.3 -> LINUS_262
> 1.3.1 -> parisc_262
> 1.3.1.1 -> CVS262_PA1
> 
> OK, this model clearly fits CVS' needs much better.  How about ours?
> Well, it sucks that you're always developing on a branch.  It sucks for
> people who're used to doing 'cvs up -A' to get to the trunk, because
> they now get Linus instead of us.  It also sucks that you stay on
> parisc_261 when you type "cvs up", so you have to explictly say "cvs
> up -rparisc_262".
> 
> However, it doesn't have the suckitude of vendor branches, and it allows
> us to reasonably use cvs diff -rlinus.  Choose your suck.

The proposed model works OK.  I used to use it for my voyager trees when
I had them in CVS instead of BK.  I think your assessment is correct:
it's the least of the evils.

James