2.6.24 - time to switch

[Werner Almesberger]

Hi Mickey,

I think it's time to face down our fears and finally switch our
principal tree from 2.6.22.5 to 2.6.24.

This will probably upset some things, so it may be good if any
"trustworthy and stable" builds don't pick up the changes yet, but
everyone else should. The sooner we fish out the bugs, the better
for all involved.

Now, I thought a bit about how we can bring the great change about
in SVN, and since this is the first time I get to do this, I'd
appreciate some advice. As far as I can tell, there are two options:

1) Make a server-side copy such that we have brief changelog telling
   which files have changed, or
2) make a client-side copy and get all the the differences in the
   changelog.

I did a diff on the two patchsets and 2) would yield about 10'000
lines or 320kB. Since there is quite a bit of useful information in
these diffs (besides copious amount of noise, as one would expect),
I'd lean towards option 2).

Does this sound good ?

I think 2) can be adequately implemented by

  ( cd trunk/src/target/kernel/patches && svn remove *)
  cp branches/src/target/kernel/2.6.24.x/patches/* \
     trunk/src/target/kernel/patches
  cd trunk/src/target/kernel/patches
  svn add *
  svn commit

Would you agree with this ?

- Werner