Stefan Beller wrote: > We also want to have 4b9ab0ee0130~1^2 to work `right`, in the sense > that not just the hexadecimals are highlighted and linking to > 4b9ab0ee0130, but the whole expression should link to 49e863b02ae177. Presumably the same logic which finds 4b9ab0ee0130 to link it can also see if it is suffixed with '~1^2' ? Is a ref like 4b9ab0ee0130~1^2 commonly useful? In cmake we use the output of cmake describe --contains (when there is a following tag) to refer to commits, in a pattern which I've also seen in git.git occasionally: https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=23f3798c I think the only reason for using the output of cmake describe --contains is that it shows the reader the 'era' of the commit (and release it appears in) without having to look it up. I'm not really aware of another good reason to use it, but I think that's enough to make sense. However I'm not sure I understand why anyone would refer to 4b9ab0ee0130~1^2 instead of 49e863b0 (or perhaps v2.6.5~12, depending on whether the tag is there). >> What does 'HEAD^' mean? If it is 'the commit before this one', then why >> not link it? > > As said I was thinking about the git development > I do not think we would want to link HEAD to anything in that example. > (I'd have no idea what it would link to here, so just not link it?) Right, so if a commit message contains something like Make git rebase -i HEAD^^^^ ten times better then HEAD^^^^ shouldn't become a link. Makes sense to me. Thanks, Steve. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html