Welcome to the 47th edition of Git Rev News, a digest of all things Git. For our goals, the archives, the way we work, and how to contribute or to subscribe, see the Git Rev News page on git.github.io.
This edition covers what happened during the month of December 2018.
Ævar Arnfjörð Bjarmason replied to a patch that Jonathan Nieder had sent to the mailing list. He suggested using the standard commit-reference format documented in SubmittingPatches in the commit message of the patch.
Using the standard format would have produced:
92068ae8bf ("stripspace: respect repository config", 2016-11-21)
while Jonathan’s patch contained:
v2.11.0-rc3~3^2~1 (stripspace: respect repository config, 2016-11-21)
The main difference is that the former starts with an abbreviated
object id, while the latter starts with an output from
Ævar gave an example of him previously looking for a commit using
git log --grep=0386dd37b1 and not finding it because Jonathan had
not used the standard format.
Ævar also wondered if “we should have some mode where
--grep=<commitish> will be combined with some mode where we try to
find various forms of
<commitish> in commit messages, then normalize
& match them…”
Duy Nguyen replied to that by suggesting we use email style trailers
In-Reply-To: ... or even
Fixes: ... to refer
to related commits, which could make sense as we already use
Signed-off-by: User <email> trailers
and some other similar trailers in commit messages.
Gábor Szeder also replied to Ævar saying that the
%h (%s, %ad) is
even better and more widely used than the standard
%h ("%s", %ad) as
the former avoids useless double quotes around the commit title.
Jeff King, alias Peff, then commented to Ævar’s suggestion about a new
--grep=<commitish>. He gave examples of other tools that
work better with the standard format:
web interfaces like GitHub have learned to replace an abbreviated object id with a link to a page displaying the object,
terminals makes it easy to select object ids, but don’t understand
Peff acknowledged that the format with an output from
has some benefits:
As far as I can tell, the main advantage of using
v2.11.0-rc3~3^2~1over its hex id is that it gives a better sense in time of which Git version we’re talking about. The date in the parentheses does something similar for wall-clock time, but it’s left to the reader to map that to a Git version if they choose.
But he thought that they were not worth the disadvantages “as in the
rare instance that I care about the containing version, it’s not a big
deal to use
git tag --contains”.
He suggested anyway using something like:
1234abcd (the subject line, 2016-01-01, v2.11.0)
which adds a version after the date, “if we really want to convey that information”. And he proposed some reasonable rules for this new format.
Jonathan replied to Peff’s suggestion by discussing the possible
ambiguities in what the tag name is referring to. This led Jonathan to
prefer using trailers like
Fixes: ... as Duy had suggested,
saying they have been working well for the Linux kernel project.
In a separate reply to Duy’s email, Jonathan copied relevant documentation from the Linux kernel project where they specify a trailer that looks like:
Fixes: e21d2170f366 ("video: remove unnecessary platform_set_drvdata()")
Jonathan then proposed a patch to the Git Documentation that would make the Git project adopt a similar policy.
Peff replied to Jonathan that using
Fixes: ... trailers is a good
idea but that “there are many other reasons to refer to another commit
in prose (or even outside of a commit message entirely)”.
Jonathan, Peff and Ævar discussed a bit more, and Jacob Keller chimed in, but in the end it doesn’t look like any change has been decided.
Git tools and sites
This edition of Git Rev News was curated by Christian Couder <firstname.lastname@example.org>, Jakub Narębski <email@example.com>, Markus Jansen <firstname.lastname@example.org> and Gabriel Alcaras <email@example.com> with help from Johannes Schindelin, Robin Shen and David Pursehouse.