From: Sasha Levin <sashal@kernel.org>
To: torvalds@linux-foundation.org
Cc: 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,
willy@infradead.org, workflows@vger.kernel.org, kees@kernel.org
Subject: Re: [PATCH] git-disambiguate: disambiguate shorthand git ids
Date: Thu, 26 Dec 2024 17:32:57 -0500 [thread overview]
Message-ID: <Z23ZmVwgS2ErX-dj@lappy> (raw)
In-Reply-To: <20241226220555.3540872-1-sashal@kernel.org>
On Thu, Dec 26, 2024 at 05:05:55PM -0500, Sasha Levin wrote:
>This also allows users to use shorter commit ID prefixes than normally
>required, since we can correctly identify the intended commit using the
>subject line as additional context.
With this script, and a git alias:
git config --global alias.klog '!sh -c '"'"'last=""; next_to_last=""; args=""; for arg in "$@"; do [ -n "$next_to_last" ] && args="$args $next_to_last"; next_to_last="$last"; last="$arg"; done; hash=$(git-disambiguate.sh "$next_to_last" "$last") && git log $args "$hash"'"'"' -'
We can have (git-log compatible) git-klog find the right commit for us:
$ git klog --oneline -1 cff8 '("net: phy: avoid ... *_led_polarity_set()")'
cff865c70071 net: phy: avoid undefined behavior in *_led_polarity_set()
Which means that folks should be able to use a fairly short abbreviated
commit IDs in messages, specially for commits with a long subject line.
--
Thanks,
Sasha
next prev parent reply other threads:[~2024-12-26 22:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-26 22:05 [PATCH] git-disambiguate: disambiguate shorthand git ids Sasha Levin
2024-12-26 22:32 ` Sasha Levin [this message]
2024-12-26 23:33 ` Linus Torvalds
2024-12-27 0:55 ` Sasha Levin
2024-12-27 1:50 ` Linus Torvalds
2024-12-27 16:19 ` Sasha Levin
2024-12-27 18:33 ` Geert Uytterhoeven
2024-12-27 19:07 ` Sasha Levin
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=Z23ZmVwgS2ErX-dj@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=willy@infradead.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).