linux-kernel - Re: [GIT pull] scheduler updates for 5.1

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: <CAHk-=wixSEaRjAPT8ZiJhbs-5phzjSrRktz7tOCdSe5OCixfmA@mail.gmail.com>
Date:   Sun, 24 Mar 2019 11:48:40 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Thomas Gleixner <tglx@...utronix.de>
Cc:     Linux List Kernel Mailing <linux-kernel@...r.kernel.org>,
        "the arch/x86 maintainers" <x86@...nel.org>
Subject: Re: [GIT pull] scheduler updates for 5.1

On Sun, Mar 24, 2019 at 11:39 AM Thomas Gleixner <tglx@...utronix.de> wrote:
>
> Now doing a fresh clone from git.k.org (not ssh) shows me the stale commit
> from last week.

Now it gets me the right thing too.

Note that I have some git magic that means that I always pull from the
ssh side of kernel.org, just to avoid any stale issues:

 - my ~/.gitconfig does url rewriting to use the ssh//gitolite address

 - I have a prepare-commit-msg hook that then re-writes the ssh
address to the public address

so it wasn't due to mirroring latency.

Whatever. It looks right to me now, so I've pulled it.

               Linus