linux-kernel - Re: [GIT PULL] Documentation for 6.14

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] [day] [month] [year] [list]

Message-ID: <CAHk-=wjku9Su_1A0dWYVNkGaLnRgNaf7dijLeL3k1GVbQzCaeQ@mail.gmail.com>
Date: Wed, 22 Jan 2025 08:02:35 -0800
From: Linus Torvalds <torvalds@...uxfoundation.org>
To: Jonathan Corbet <corbet@....net>
Cc: linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org
Subject: Re: [GIT PULL] Documentation for 6.14

On Wed, 22 Jan 2025 at 05:58, Jonathan Corbet <corbet@....net> wrote:
>
> I took it because it seemed that consistency in the documentation was
> better than conflicting advice.  If the policy is really "exactly 12
> characters", though, we should probably make it read that way
> instead...?

Well, I don't think it needs to be some hard "exactly 12". At some
point in the future, you *will* get collisions (Konstantin already
created a tree for that exact thing) and git will automatically give
you 13 or more characters.

But I also don't want to encourage people for no good reason to go
overboard, and we end up with extra line noise, and commit ID's that
don't line up nicely etc. The whole "12 characters isn't enough" isn't
actually the real and present problem we have (and there was a whole
long discussion about the things that _are_ problems).

                Linus