linux-kernel - Re: [GIT PULL] PCI changes for v4.11

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+55aFx1L0rhBHRRsgDch31aU+Y-8C=tiFZHUnL2wnrifi+yVw@mail.gmail.com>
Date:   Thu, 23 Feb 2017 11:35:46 -0800
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Bjorn Helgaas <helgaas@...nel.org>
Cc:     "linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] PCI changes for v4.11

On Thu, Feb 23, 2017 at 10:15 AM, Bjorn Helgaas <helgaas@...nel.org> wrote:
>
>   git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git c4d052ce970e

Ok, so this is just strange.

I do not generally pull the random SHA1's directly, I want a branch
name or a tag-name.

(Honesty in advertising: I *have* pulled the direct SHA name in the
past, simply because I didn't want to pull a whole branch. But then I
edit up the end result to have a sensible name, because I want one).

So I don't take pull requests that don't have sane branch or tag
names. Because that's just odd.

Please fix up you repository. Or ratrher, please fix your pull
request. Because what I think I actually want to pull is

    tags/pci-v4.11-changes

which is the signed tag that you have that actually points to that
commit. But you use some completely broken request-pull script that
screwed everything up.

Please just burn that piece of crap code on the altar to the goddess
of good taste.

           Linus