kernel patch/repository status

[Werner Almesberger]

Sven Rebhan wrote:
> However, I would like to ask you to create a new stable branch,
> tracking 2.6.29.y releases + openmoko patches until 2.6.30 is out.

Hmm, how would that "stable" branch differ from what I've outlined ?
My idea is to work on just one branch while restructuring, in order
to make this as quick and painless as possible. All our other
non-upstream branches would become obsolete after that.

So anyone looking for stability in the next days should probably just
pick a branch and head they like and stick with it until the storm is
over.

> To
> base the openmoko branch on linus (or rmk's ???) tree is also a good
> idea to be able to push things upstream.

Yes, Linux, rmk, or even Ben are potential candidates for a basis.
The branching point is fortunately a choice we can revise in the
future.

I think the main question for selecting the ideal point is how
closely we have to exchange changes with that upstream branch (both
ways) and how much they get modified on their way to Linus.

I.e., if we pull tons of changes we don't care about and they all
get heavily edited before tricking down from Linus again, then
we've created an enormous amount of work for nothing. At the same
time, waiting weeks for urgent fixes for blockers (or having to
cherry-pick every little change) wouldn't do us any good either.

> In the same direction, how are your plans for upstream submission? It
> would be good to get some feedback on mach-gta02 (in the proposed
> branch)...

Upstream submission is still in shambles right now. I think it'll stay
that way for a few days, until we have time to sort out that process.

- Werner