diff options
author | Denton Liu <liu.denton@gmail.com> | 2019-11-19 16:51:25 -0800 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2019-11-20 13:33:37 +0900 |
commit | 1f0fc1db8599f87520494ca4f0e3c1b6fabdf997 (patch) | |
tree | 8d49fd7aa011a813f90e2dd9c4bc21648fe4b5e6 /Documentation/git-range-diff.txt | |
parent | pretty: add struct cmt_fmt_map::default_date_mode_type (diff) | |
download | tgif-1f0fc1db8599f87520494ca4f0e3c1b6fabdf997.tar.xz |
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>
Diffstat (limited to 'Documentation/git-range-diff.txt')
0 files changed, 0 insertions, 0 deletions