Re: Linux 2.5.0

[Wayne.Brown@altec.com]

Yes, I realize that.  When switching from one tree to another I reverse the
patches back to the fork point (using patch -R) and then apply the appropriate
patches for the tree I want.  That's the method I've used for a long time for
keeping up with both Linus' -preX kernels and Alan's -acX kernels with only a
single source tree.  (After 2.5 has been out for awhile I'll just drop 2.4
altogether and then it won't be an issue.)

Wayne




Arnaldo Carvalho de Melo <acme@conectiva.com.br> on 11/25/2001 10:51:28 AM

To:   Wayne Brown/Corporate/Altec@Altec
cc:   lkml <linux-kernel@vger.kernel.org>

Subject:  Re: Linux 2.5.0



Em Sun, Nov 25, 2001 at 09:16:17AM -0600, Wayne.Brown@altec.com escreveu:
>
>
> Thanks.  I had hoped the version number was the only change, but wanted to be
> sure.  I'll be keeping just one source tree for both 2.4.x and 2.5.x and
> switching between the versions by applying and reversing patches as needed, so
> it's important that my copy of the source stay *exactly* in sync with Linus'

But keep in mind that this is only the fork point, from now on more and
more things will diverge and patches for one will not necessarily apply to
both trees.

> copy (otherwise I've have just altered the version in the Makefile myself).
> With the help of your patch I've just built both 2.4.16-pre1 and 2.5.1-pre1
from
> the same 2.4.15 source, which is what I wanted.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/