[linuxsh-dev] Kernel Update Permission?

[NIIBE Y. <gn...@m1...>]

Thanks, Jeremy and Paul.  For me, no problem at all.  Go ahead for
drop'in tree.

Jeremy Siegel wrote:
 > so are there any objections to an attempt to update the current
 > drop-in tree?

No.

 > 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?

Yes.  I don't care for 2.4.1[45].

 > Is there some reason to wait?

I don't think we have.

BTW, someone sent me the note about we should _not_ use SourceForge
anymore for the sake of freedom, but I don't think it's relevant for
our usage.

			*	*	*

I haven't been able to doing for SuperH kernel things for a while,
sorry for no response.

While we're working for submitting patches to GCC list, well, everyone
knows, I've found it's quite hard to maintain patches and keep it
up-to-date against _current_ GCC.

I have been learning (somewhat special) CVS usage to avoid patch being
obsolete and losing someware, that is, mirroring CVS, using local branch
such as 1.1.999.  I'm not sure how it works, but I think that all the
changes required for GCC is now well maintained (better).
--