linux-kernel - Re: [GIT PULL] block fixes for 3.9-rc

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 for Android: free password hash cracker in your pocket

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

Message-ID: <CA+55aFwoj=g0YrFOrpoKNY43o8qDAhDEHSP-zrtpWCXciwz_-Q@mail.gmail.com>
Date:	Fri, 29 Mar 2013 11:08:40 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Jens Axboe <axboe@...nel.dk>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] block fixes for 3.9-rc

On Fri, Mar 29, 2013 at 8:38 AM, Jens Axboe <axboe@...nel.dk> wrote:
>
> Please pull! As per usual, it's tagged and signed.

No it's not.

You have a *branch* called for-linus that contains the commits you mention.

And then you have a *tag* called for-linus, but that's just my old
head that you've gone ahead and signed, which is entirely and utterly
pointless.

Christ, the amount of confusion in that tree.  Don't alias tags and
branches. And if you do, make it clear which one you mean by *saying*
so, ie "tags/for-linus", not just the ambiguous "for-linus". Now
you've confused yourself, and because of the ambiguity you never even
noticed, because the *branch* for-linus had the right commits.

Don't do this kind of thing. That branch is pointless, and just confused you.

                     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/