Proposal for further openmoko kernel development
werner at openmoko.org
Wed Jul 29 02:13:17 CEST 2009
Lars-Peter Clausen wrote:
> Well, depends on your definition of 'a lot'. We would probably end
> up with ~10 driver trees + 3 machine trees + 1 all tree = ~ 15
Heh, 15 trees for about 5 active committers. Still sounds like a
> And my proposed structure makes upstream inclusion a lot easier
> since you always have all changes to get a driver support in a
> single patchset. Instead of having to pick it from the huge series
> of patches which contain everything.
So ... is what you're really after topic branches ? Wouldn't they
be better implemented by having a branch per topic, which is removed
once the issue has been resolved and pushed upstream ? If a driver
doesn't have any pending work, there would be no branch for it.
Topics could be "driver foo general maintenance", but they might
also be more specific, so that you don't end up with a "driver foo"
branch that has interconnected topics "great renaming in foo" and
"foo API change" rolled into one patch.
More information about the openmoko-kernel