Hi, > 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.
Agreed. > 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. Absolutely. > 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). Me too. It may be a bit overwhelming for our CIAbot, but that's about it :) > > 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 ? svn cp retains the history, so you should be able to use this instead of the (cp, add) tuple. :M:
