[linuxsh-dev] Kernel Update Permission?

[Jeremy S. <js...@mv...>]

Hi folks,

Some weeks ago Paul Mundt and I sent a tarball to SourceForge to replace
the
current drop-in tree with a nearly identical version including the old
history; I
expected to check in a 2.4.14 update when that happened.

However, it hasn't happened yet and we've no indication when it will; so
are
there any objections to an attempt to update the current drop-in tree?
I've not
done this before but I think it's straightforward CVS; no vendor imports
and
such like the old kernel module, just a few shared files which change.

I'd expect to do something like:
  1. Tag the current 2.4 branch as 13-pre2.
  2. Check in changes in the 2.4 branch for 2.4.15, updating AGAINST too.
  3. Tag the 2.4 branch as 2.4.15.
  4. Check in changes in the 2.4 branch for 2.4.16.
  5. Check in same changes as (2) in 2.5 branch, update AGAINST as needed.

Seem reasonable?  Or should I skip the 2.4.15 in the 2.4 branch
altogether?
(Alternatively, I could add a 2.4.14 check-in and tag, I suppose.)  Is
there
some reason to wait?  Would someone else prefer to do this?

Thanks for any feedback,

--Jeremy Siegel