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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20130329182411.GD2567@kernel.dk>
Date:	Fri, 29 Mar 2013 12:24:11 -0600
From:	Jens Axboe <axboe@...nel.dk>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
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, Linus Torvalds wrote:
> 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.

Oops, that was a mistake. I must have been on the wrong branch at that
point. In past requests, I've signed the for-linus (or topic) branch
specifically.

> 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.

Agree, the aliasing is nasty and git checkout usually doesn't like it a
whole lot either...

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

Tag, you mean?

-- 
Jens Axboe

--
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/