-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Somebody in the thread at some point said: | OK, I've redone the entire patch set based on sound-2.6. I've | cherry-picked everything we need from there and reimplemented my | changes on top of that...
Wah quick! | Now the question is: how do you want this? Should I: | | 1) Resubmit patches against stable tracking from this morning? | 2) Or against stable-tracking as it is now (with my changes already | integrated)? This will be messy with the cherry-picks from sound-2.6 | unless I "revert" the changes first. | 3) Or...? | | Do you prefer a git tree to pull from? #1 is best, I will drop the first patchset and replace them with this. The tracking stuff isn't maintaining a history. It's OK on the list, I have some scripts to help me process them and that way we get people looking at them at the same time. - -Andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkjj0RkACgkQOjLpvpq7dMpBJgCfetA+gZwPax2mqmeyXUnndzRz ticAmweFSF0Qwc+gXLadaMcHfQd+rRjL =1nEo -----END PGP SIGNATURE-----
