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+55aFxj4Oe8+DbNLzk+SKoW99MTeF+m1SAiC4hgW=bN2dpvEQ@mail.gmail.com>
Date:   Wed, 10 May 2017 17:47:50 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     "Eric W. Biederman" <ebiederm@...ssion.com>
Cc:     Al Viro <viro@...iv.linux.org.uk>,
        Thomas Gleixner <tglx@...utronix.de>,
        Oleg Nesterov <oleg@...hat.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Is there an recommended way to refer to bitkeepr commits?

On Wed, May 10, 2017 at 3:04 PM, Eric W. Biederman
<ebiederm@...ssion.com> wrote:
>
> Thomas Gleixner appears to have a tree with all of those same commits
> except with the BKrev tags stripped out.

That's the best import - so use that tree by Thomas, and just use the
git revision numbers in it (and say "tglx's linux-history tree" or
something).

             Linus

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ