Hi Guennadi, On Thu, Jun 28 2012, Guennadi Liakhovetski wrote: > There are a number of MMC patches from me outstanding for 3.6. > Appreciating, that it might not be very easy to keep on overview - what > latest versions are and in which order they should be applied - would you > like me to either assemble a list of patches with links to ML archives or > maybe set up a git branch somewhere on github? In the latter case - would > you require some signing process - if it is at all supported on github. > No, I never used one, but I'd have a look if you prefer me to use one. > > We still have some time until 3.6 merge window, but it would be nice to > let patches simmer for a while in -next. Thanks, a github branch based on mmc-next would be great, and you don't need to sign it. If you have gpg setup but don't want to learn how to use git signed tags yet, something you could do is sign the e-mail that "git request-pull" generates that says "pull from url <foo> to go from commit <hash> to a new HEAD hash of <hash>". (This effectively signs all the commits, because applying all of the correct commits is the only way to get to that new hash, and I can verify that I have that hash as my new HEAD after pulling.) - Chris. -- Chris Ball <cjb@xxxxxxxxxx> <http://printf.net/> One Laptop Per Child -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
