From: Chris Ball <cjb@laptop.org>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-mmc@vger.kernel.org, Magnus Damm <magnus.damm@gmail.com>
Subject: Re: My outstanding MMC / SDHI/TMIO / MMCIF patches for 3.6
Date: Thu, 28 Jun 2012 10:29:02 -0400 [thread overview]
Message-ID: <87sjdf8q8h.fsf@octavius.laptop.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1206281029270.31813@axis700.grange> (Guennadi Liakhovetski's message of "Thu, 28 Jun 2012 10:36:13 +0200 (CEST)")
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@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2012-06-28 14:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 8:36 My outstanding MMC / SDHI/TMIO / MMCIF patches for 3.6 Guennadi Liakhovetski
2012-06-28 14:29 ` Chris Ball [this message]
2012-06-29 15:03 ` Guennadi Liakhovetski
2012-06-29 16:26 ` Chris Ball
2012-06-29 18:44 ` Guennadi Liakhovetski
2012-06-29 23:25 ` Chris Ball
2012-06-30 10:45 ` Guennadi Liakhovetski
2012-06-30 12:52 ` Chris Ball
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sjdf8q8h.fsf@octavius.laptop.org \
--to=cjb@laptop.org \
--cc=g.liakhovetski@gmx.de \
--cc=linux-mmc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox