-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Chris On Fri, 29 Jun 2012, Chris Ball wrote: > Hi, > > On Fri, Jun 29 2012, Guennadi Liakhovetski wrote: > > Hi Chris > > > > On Thu, 28 Jun 2012, Chris Ball wrote: > >> 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.) > > > > Ok, let's try, no guarantee though :) Let me know if there are any > > problems with my signing exercise. > > > > The following changes since commit ed99260f748d4c1894a23a4519fd59156a27a308: > > > > mmc: tmio: remove a duplicated comment line (2012-06-26 16:10:40 -0400) > > > > are available in the git repository at: > > https://github.com/lyakh/linux.git mmc-for-3.6 > > Close, but you didn't tell me what the new HEAD hash should be after > pulling. This means that the patches could be modified on github > and as long as the diffstat doesn't change, there's no way for me > to know that I'm not pulling what you think I'm pulling. > > So, just tell me (in a signed mail) what the top commit's hash is for > you, and that'll prove I'm getting what you're sending. Ah, ok, right, sorry, I thought, it would be a part of the "git request-pull" output. So, the top commit has hash 7c4cf5b31b98f51ebfc8db89b022e4f52f93f5db Hope, this is what's required :-) Thanks Guennadi - --- Guennadi Liakhovetski, Ph.D. Freelance Open-Source Software Developer http://www.open-technology.de/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk/t96IACgkQU6Nrc+zHHwgIUgCeNZFGp71QoqiZ1VB2oE+Pe5KA VlcAoJwdgZ59L6l52QBxuC8CYFSSvddX =WTuB -----END PGP SIGNATURE----- -- 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
