linux-kernel - Re: [git patches] libata updates for 3.5

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+55aFwb-cMTuEFaOW=zwLyk_J8eeLkUs-D0DRO7r-9t7k5crQ@mail.gmail.com>
Date:	Wed, 23 May 2012 15:28:09 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Jeff Garzik <jeff@...zik.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-ide@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [git patches] libata updates for 3.5

On Wed, May 23, 2012 at 2:35 PM, Jeff Garzik <jeff@...zik.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").

                    Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/