]> git.ipfire.org Git - thirdparty/git.git/commit - contrib/completion/git-completion.bash
pretty: implement 'reference' format
authorDenton Liu <liu.denton@gmail.com>
Wed, 20 Nov 2019 00:51:25 +0000 (16:51 -0800)
committerJunio C Hamano <gitster@pobox.com>
Wed, 20 Nov 2019 04:33:37 +0000 (13:33 +0900)
commit1f0fc1db8599f87520494ca4f0e3c1b6fabdf997
tree8d49fd7aa011a813f90e2dd9c4bc21648fe4b5e6
parent618a855083fbd3b8f9491ec8b32b39bdea91868d
pretty: implement 'reference' format

The standard format for referencing other commits within some projects
(such as git.git) is the reference format. This is described in
Documentation/SubmittingPatches as

If you want to reference a previous commit in the history of a stable
branch, use the format "abbreviated hash (subject, date)", like this:

....
Commit f86a374 (pack-bitmap.c: fix a memleak, 2015-03-30)
noticed that ...
....

Since this format is so commonly used, standardize it as a pretty
format.

The tests that are implemented essentially show that the format-string
does not change in response to various log options. This is useful
because, for future developers, it shows that we've considered the
limitations of the "canned format-string" approach and we are fine with
them.

Based-on-a-patch-by: SZEDER Gábor <szeder.dev@gmail.com>
Signed-off-by: Denton Liu <liu.denton@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/pretty-formats.txt
Documentation/pretty-options.txt
Documentation/rev-list-options.txt
contrib/completion/git-completion.bash
pretty.c
t/t4205-log-pretty-formats.sh