Hello all,
the ALSA server has new alsa-driver repository which contains several branches for now:
master - just empty one with README build - the previous master branch (but all was moved to the alsa/ subtree) mirror - mirrored code from upstream (ALSA parts only) release - merging branch for mirror/build trees to create a relationship between them
All branches are ophan. It means that they have no common parent.
I put some handy configuration hints to the ALSA WIKI:
http://www.alsa-project.org/main/index.php/GIT_Server#Syncing_the_branch_rel...
The reason to move the old master branch to the alsa/ subtree is quite simple - you can merge/pull the branch to the full linux-2.6 kernel tree now and do your development there. Also, cherry picks between mirror and the linux-2.6 tree should work.
Another handy extension - in the current repo - might be to create the linux-2.6 branch with the whole upstream and create another branch for merging the build branch with the whole tree like 'release26' or so. In this way, we can manage another releases of the out-of-kernel build code for the ALSA tree in stable linux kernel versions.
Comments, other ideas are welcome.
Jaroslav