From: Jeff Garzik <jeff@garzik.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-ide@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git patches] libata updates for 3.5
Date: Wed, 23 May 2012 19:47:48 -0400 [thread overview]
Message-ID: <4FBD7724.1050503@garzik.org> (raw)
In-Reply-To: <CA+55aFwb-cMTuEFaOW=zwLyk_J8eeLkUs-D0DRO7r-9t7k5crQ@mail.gmail.com>
On 05/23/2012 06:28 PM, Linus Torvalds wrote:
> On Wed, May 23, 2012 at 2:35 PM, Jeff Garzik<jeff@garzik.org> wrote:
>>
>> hmmm, can you try again? The output of
>>
>> http://git.kernel.org/?p=linux/kernel/git/jgarzik/libata-dev.git;a=summary
>>
>> and
>>
>> http://git.kernel.org/?p=linux/kernel/git/jgarzik/libata-dev.git;a=tag;h=4560c1c455fb87ba3013967d6ed5d0b1d18cc109
>>
>> looks correct, so I think there was a mirroring delay.
>
> No. Look closers.
>
> You've created a tag called "tag/upstream-linus", and that's the one
> you asked me to pull.
>
> But looking at gitweb, there is *also* a tag called just
> "upstream-linus", and that's the one you probably *meant* me to pull.
>
> If you had asked me to pull "tags/upstream-linus" (note: "tags/" vs
> "tag/"), that would have indicated that it's in the "tags" namespace
> and I would have gotten the one you meant.
>
> I'd suggest you delete the old confused "tag/upstream-linus" tag (aka
> "tags/tag/upstream-linus").
Bogus tag/upstream-linus deleted, and push script updated. This is the
head of the new output:
Please pull 2fff27512600f9ad91335577e485a8552edb0abf from
git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
tags/upstream-linus
prev parent reply other threads:[~2012-05-23 23:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 19:28 [git patches] libata updates for 3.5 Jeff Garzik
2012-05-23 21:06 ` Linus Torvalds
2012-05-23 21:35 ` Jeff Garzik
2012-05-23 22:28 ` Linus Torvalds
2012-05-23 23:47 ` Jeff Garzik [this message]
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=4FBD7724.1050503@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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