Re: Referring to commits in commit messages
- Date: Wed, 19 Dec 2018 10:39:27 -0800
- From: Jonathan Nieder <jrnieder@xxxxxxxxx>
- Subject: Re: Referring to commits in commit messages
Jeff King wrote:
> - web interfaces like GitHub won't linkify this type of reference
> (whereas they will for something that looks like a hex object id)
> - my terminal makes it easy to select hex strings, but doesn't
> understand this git-describe output :)
> These tools _could_ be taught a regex like /v(\d+.)(-rc\d+)?([~^]+d)*/.
> But matching hex strings is a lot simpler, and works across many
Is there some rule about how long the hex string has to be for this to
> In commit 1234abcd (the subject line, 2016-01-01, v2.11.0), we did
> blah blah blah
The issue with this is that it is ambiguous about what the tag name is
referring to: does that mean that "git describe" and "git version"
tell me that v2.11.0 is the nearest *previous* release to that commit
or that "git name-rev" tells me that v2.11.0 is a nearby *subsequent*
release that contains it?
Of course the latter is the only answer that's useful, but in practice
the former is what people tend to do when they are trying to follow a
convention like this. So we'd need some automatic linting to make it
I think a more promising approach is the Fixes trailer Duy mentioned,
which has been working well for the Linux kernel project. I'll follow
up in a reply to his message.