From: Chris Ball <cjb@laptop.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] MMC fixes for 3.4-rc2
Date: Fri, 06 Apr 2012 20:51:31 -0400 [thread overview]
Message-ID: <87haww2wks.fsf@laptop.org> (raw)
In-Reply-To: <CA+55aFxSARUvsOGX6s5MoH+i_Pw6kU=Qt3Z1Ei_1xvJWFcx8kQ@mail.gmail.com> (Linus Torvalds's message of "Fri, 6 Apr 2012 17:22:10 -0700")
Hi Linus,
On Fri, Apr 06 2012, Linus Torvalds wrote:
> On Fri, Apr 6, 2012 at 12:35 PM, Chris Ball <cjb@laptop.org> wrote:
>>
>> Please pull from:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/cjb/mmc.git for-linus
>>
>> to receive MMC fixes for 3.4-rc2. I've signed an "mmc-fixes-for-3.4-rc2"
>> tag.
>
> Please just ask my to pull the tag directly, don't say "please pull
> this branch", and then add "oh, but there's this tag also".
>
> I already did the "cut-and-paste" for the pull, and then I realized
> that I'm not seeing the message that your email implied was there, and
> then I noticed that you talked about the tag separately.
>
> That just messes everything up. Don't even bother mentioning the
> worthless branch. The tag has everything the branch has, _and_ the
> message.
>
> So just ask me to pull it, with a
>
> Please pull from
>
> git://git.kernel.org/pub/scm/linux/kernel/git/cjb/mmc.git
> mmc-fixes-for-3.4-rc2
>
> rather than make it unnecessarily more complicated and error-prone.
I see, sorry. I'll send just the tag from now on.
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2012-04-07 0:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-06 19:35 [GIT PULL] MMC fixes for 3.4-rc2 Chris Ball
2012-04-07 0:22 ` Linus Torvalds
2012-04-07 0:51 ` Chris Ball [this message]
2012-04-09 5:36 ` Hebbar, Gururaja
2012-04-09 5:55 ` 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=87haww2wks.fsf@laptop.org \
--to=cjb@laptop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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