From: Joe Perches <joe@perches.com>
To: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
linux-kernel@vger.kernel.org,
"Linus Torvalds" <torvalds@linux-foundation.org>
Cc: Andy Whitcroft <apw@canonical.com>,
Dwaipayan Ray <dwaipayanray1@gmail.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: Re: [PATCH] checkpatch.pl: Relax commit ID check to allow more than 12 chars
Date: Sat, 04 Feb 2023 08:57:59 -0800 [thread overview]
Message-ID: <3afee0493d3718f2e38b6c54dab23d38360cd5d0.camel@perches.com> (raw)
In-Reply-To: <78d224a63f6c27bf700d59007b6f3c89746d728c.camel@perches.com>
On Sun, 2023-01-29 at 09:52 -0800, Joe Perches wrote:
> On Sun, 2023-01-29 at 13:34 +0100, Jonathan Neuschäfer wrote:
> > By now, `git log --pretty=%h` (on my copy of linux.git) prints commit
> > hashes with 13 digits, because of the number of objects.
> >
> > Relax the rule in checkpatch.pl to allow a few more digits (up to 16).
>
> NAK without updating the process docs first.
btw: it looks like 12 will still be sufficient for awhile yet
$ git count
total 1154908
$ git -c core.abbrev=5 log --pretty=format:%h | \
perl -nE 'chomp;say length' | sort | uniq -c | sort -n -k2
198 5
664613 6
450955 7
36667 8
2312 9
155 10
8 11
next prev parent reply other threads:[~2023-02-04 16:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-29 12:34 Jonathan Neuschäfer
2023-01-29 17:52 ` Joe Perches
2023-01-31 21:00 ` Jonathan Neuschäfer
2023-02-04 16:57 ` Joe Perches [this message]
2023-02-05 10:40 ` Jonathan Neuschäfer
2023-02-05 16:33 ` Randy Dunlap
2023-02-05 20:38 ` Linus Torvalds
2023-02-06 8:38 ` Geert Uytterhoeven
2023-02-06 11:09 ` Joe Perches
2023-02-06 11:54 ` Geert Uytterhoeven
2023-02-06 12:25 ` Joe Perches
2023-02-07 14:47 ` Jonathan Neuschäfer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3afee0493d3718f2e38b6c54dab23d38360cd5d0.camel@perches.com \
--to=joe@perches.com \
--cc=apw@canonical.com \
--cc=dwaipayanray1@gmail.com \
--cc=j.neuschaefer@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®