summaryrefslogtreecommitdiff
path: root/submodule-config.h
diff options
context:
space:
mode:
authorLibravatar Cornelius Weig <cornelius.weig@tngtech.com>2017-02-08 23:41:18 +0100
committerLibravatar Junio C Hamano <gitster@pobox.com>2017-02-08 15:43:27 -0800
commitdf8512ede80888505b15ab92efc70f2f20f3cba8 (patch)
tree36ccea112c2532d7a1e4a27713507119cf6f57f3 /submodule-config.h
parentGit 2.11.1 (diff)
downloadtgif-df8512ede80888505b15ab92efc70f2f20f3cba8.tar.xz
tag: generate useful reflog message
When tags are created with `--create-reflog` or with the option `core.logAllRefUpdates` set to 'always', a reflog is created for them. So far, the description of reflog entries for tags was empty, making the reflog hard to understand. For example: 6e3a7b3 refs/tags/test@{0}: Now, a reflog message is generated when creating a tag, following the pattern "tag: tagging <short-sha1> (<description>)". If GIT_REFLOG_ACTION is set, the message becomes "$GIT_REFLOG_ACTION (<description>)" instead. If the tag references a commit object, the description is set to the subject line of the commit, followed by its commit date. For example: 6e3a7b3 refs/tags/test@{0}: tag: tagging 6e3a7b3398 (Git 2.12-rc0, 2017-02-03) If the tag points to a tree/blob/tag objects, the following static strings are taken as description: - "tree object" - "blob object" - "other tag object" Signed-off-by: Cornelius Weig <cornelius.weig@tngtech.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'submodule-config.h')
0 files changed, 0 insertions, 0 deletions