[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7c353e1ba4025dfce4c4789033f5779c4371f048.camel@perches.com>
Date: Tue, 05 Dec 2023 12:05:37 -0800
From: Joe Perches <joe@...ches.com>
To: Geert Uytterhoeven <geert+renesas@...der.be>,
Niklas Söderlund
<niklas.soderlund@...natech.se>,
Andy Whitcroft <apw@...onical.com>,
Dwaipayan Ray <dwaipayanray1@...il.com>,
Lukas Bulwahn <lukas.bulwahn@...il.com>,
Louis Peens <louis.peens@...igine.com>,
Philippe Schenker <philippe.schenker@...adex.com>,
Simon Horman <horms@...nel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Junio C Hamano <gitster@...ox.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] checkpatch: Also accept commit ids with 13-40 chars of
sha1
On Tue, 2023-12-05 at 20:34 +0100, Geert Uytterhoeven wrote:
> Documentation/dev-tools/checkpatch.rst says:
>
> **GIT_COMMIT_ID**
> The proper way to reference a commit id is:
> commit <12+ chars of sha1> ("<title line>")
It's not just checkpatch.
Documentation/process/submitting-patches.rst:``git bisect``, please use the 'Fixes:' tag with the first 12 characters of
So that would need to be updated as well.
And 12 still has quite some headroom.
$ git rev-list --all --abbrev=0 --abbrev-commit | \
awk '{ a[length] += 1 } END { for (len in a) print len, a[len] }'
5 107
6 684276
7 505734
8 41769
9 2665
10 174
11 8
Powered by blists - more mailing lists