Linux 2.5.0
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 <[email protected]> on 11/25/2001 10:51:28 AM
To: Wayne Brown/Corporate/Altec@Altec
cc: lkml <[email protected]>
Subject: Re: Linux 2.5.0
Em Sun, Nov 25, 2001 at 09:16:17AM -0600, [email protected] escreveu:
Quoted 6 lines
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.
Quoted 2 lines
copy (otherwise I've have just altered the version in the
Makefilemyself). With the help of your patch I've just built both 2.4.16-pre1 and 2.5.1-pre1
from
Quoted 1 line
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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/