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 17:35:34 -0400 [thread overview]
Message-ID: <4FBD5826.3070004@garzik.org> (raw)
In-Reply-To: <CA+55aFyTDK50z7sCfRD_nzAKmWpjABxRx1f=j8i9jUUXNgHjzg@mail.gmail.com>
On 05/23/2012 05:06 PM, Linus Torvalds wrote:
> On Wed, May 23, 2012 at 12:28 PM, Jeff Garzik<jeff@garzik.org> wrote:
>>
>> Please pull 2fff27512600f9ad91335577e485a8552edb0abf from
>> git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git tag/upstream-linus
>
> That's not what I get at all. I get your old stuff that I pulled early May.
>
> I suspect you didn't force the tag update: tags aren't like branches,
> so by default git will not just overwrite an old tag with a new tag.
> Branches are *expected* to be mutable (well, at least if the changes
> are fast-forwards), after all - but changing a tag is something you
> need to be conscious about.
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.
Jeff
next prev parent reply other threads:[~2012-05-23 21:35 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 [this message]
2012-05-23 22:28 ` Linus Torvalds
2012-05-23 23:47 ` Jeff Garzik
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=4FBD5826.3070004@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