From: Sasha Levin <sashal@kernel.org>
To: Kees Cook <kees@kernel.org>
Cc: torvalds@linux-foundation.org, apw@canonical.com,
conor@kernel.org, corbet@lwn.net, dwaipayanray1@gmail.com,
geert+renesas@glider.be, gitster@pobox.com, horms@kernel.org,
joe@perches.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux@leemhuis.info,
lukas.bulwahn@gmail.com, miguel.ojeda.sandonis@gmail.com,
niklas.soderlund@corigine.com, workflows@vger.kernel.org
Subject: Re: [RFC] git-disambiguate: disambiguate shorthand git ids
Date: Thu, 19 Dec 2024 15:35:35 -0500 [thread overview]
Message-ID: <Z2SDl423NkL1QCIS@lappy> (raw)
In-Reply-To: <202412181739.0170E86E58@keescook>
On Wed, Dec 18, 2024 at 05:41:58PM -0800, Kees Cook wrote:
>On Wed, Dec 18, 2024 at 06:36:13PM -0500, Sasha Levin wrote:
>> Sometimes long commit hashes can be ambiguous even when providing
>> several digits from its abbreviation.
>
>For testing, please see:
>https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/log/?h=dev/collide/v6.13-rc2/12-char
>
>> scripts/git-disambiguate.sh | 163 ++++++++++++++++++++++++++++++++++++
>
>sfr has a bunch of logic in his "check_fixes" script that we might want
>to consolidate into here. I have an updated copy here:
>https://github.com/kees/kernel-tools/blob/trunk/helpers/check_fixes
Thanks! I'll look into it.
--
Thanks,
Sasha
prev parent reply other threads:[~2024-12-19 20:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-05 18:16 [PATCH v2 0/2] Align and increase git commit ID abbreviation guidelines and checks Geert Uytterhoeven
2024-12-05 18:16 ` [PATCH v2 1/2] Align " Geert Uytterhoeven
2024-12-30 18:43 ` Jonathan Corbet
2024-12-05 18:16 ` [PATCH v2 2/2] Increase minimum git commit ID abbreviation to 16 characters Geert Uytterhoeven
2024-12-05 19:19 ` Linus Torvalds
2024-12-13 19:41 ` Geert Uytterhoeven
2024-12-14 16:03 ` Matthew Wilcox
2024-12-14 16:31 ` Linus Torvalds
2024-12-18 23:36 ` [RFC] git-disambiguate: disambiguate shorthand git ids Sasha Levin
2024-12-19 1:41 ` Kees Cook
2024-12-19 20:35 ` Sasha Levin [this message]
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=Z2SDl423NkL1QCIS@lappy \
--to=sashal@kernel.org \
--cc=apw@canonical.com \
--cc=conor@kernel.org \
--cc=corbet@lwn.net \
--cc=dwaipayanray1@gmail.com \
--cc=geert+renesas@glider.be \
--cc=gitster@pobox.com \
--cc=horms@kernel.org \
--cc=joe@perches.com \
--cc=kees@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=lukas.bulwahn@gmail.com \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=niklas.soderlund@corigine.com \
--cc=torvalds@linux-foundation.org \
--cc=workflows@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).