Re: 2.2.16 ?

[Michel <da...@re...>]

Frank Petzold wrote:

> > > How should we go about updating the 2.2.x tree? Spawn a branch (does
> > > that work now?)?
> >
> > I'd vote for a branch (no idea how to though) just in case "stable" isn't.
> 
> Me, too ;-)

Me, too :)


> cvs tag -b merge-2-2-16
> cvs upd -r merge-2-2-16

I've done:

cvs tag -b merge_2-2-16
cvs upd -r merge_2-2-16


> "patch <unofficial-m68k-2-2-16-patch -p x" or whatever is necessary to
> migrate cvs commit

What do you people think, would it be easier to replace the whole tree with
native 2.2.16 now, then apply the m68k diff and finally try to get our stuff
back in, or rather unapply the 2.2.10 m68k diff, apply relative diffs from
2.2.10 to 2.2.16, apply the m68k and fix our stuff?


Michel


-- 
I'm so hungry, I could almost eat health food.
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86, Team *AMIGA*, AUGS