On Wed, 21 May 2008, Rene Herman wrote:
What's the status of that one now? Should I continue pulling that one or should I switch to the new alsa-kernel GIT repo? I want to pull it into a Linus clone tree...
We are working on this right now. alsa.git is far currently behind my tree.
One problem we hit is about multiple committers and rebase. If you do git-rebase, the commiter information is touched although the sign-off isn't updated. git-rebase looks apparently designed for the single-commiter model.
It's "worse" than that; rebasing is designed for a _private_ development model. git-rebase is a very handy tool for people like myself (people without a downstream that is) and it basically enables the quilt model of a stack of patches on top of git but public trees that have people pulling from them should generally not rebase or everyone who _is_ pulling finds a different tree each time.
I don't see big obstacles with this model. You can do changes in your local tree and when 'git pull' fails from the subsystem tree, pull new subsystem tree to a new branch and do rebasing in your local tree, too.
Rebasing can keep the subsystem tree more clean I think. It's only about to settle an appropriate workflow.
Jaroslav
----- Jaroslav Kysela perex@perex.cz Linux Kernel Sound Maintainer ALSA Project, Red Hat, Inc.