summaryrefslogtreecommitdiff
path: root/test/tools
diff options
context:
space:
mode:
authorJohannes Altmanninger <aclopte@gmail.com>2025-01-26 08:37:12 +0100
committerMaxime Coste <mawww@kakoune.org>2025-02-10 11:58:42 +1100
commit0a4bea856fe6ddd6420d6d7141b20eed8fe0bd25 (patch)
tree585fbf970486fc9a3f70b83516b274089dc9dc73 /test/tools
parent22b461c3a0b22dd4501943230f0774c34f0b4b35 (diff)
Format blamed commit timestamps using the original time zone
Surprisingly, these two commands show different commit times: git blame README.asciidoc kak -e 'git blame' README.asciidoc This is because git shows times as of the original time zone (of the author/committer). Our blame integration uses the current local time. - blame-jump displays the date in the status line of a git-show buffer This date may be inconsistent with the buffer's "Date:" header, so this seems surprising. Fix that. This fixes a test in some time zones. - Unlike "git blame", our ":git blame" does not display time zone info by default. So, the conversion to localtime might make sense. I don't really have an opinion on this. Change it too I guess, since the current behavior might not have been intended. Fixes #5285
Diffstat (limited to 'test/tools')
-rw-r--r--test/tools/git/blame-jump-message/script2
1 files changed, 1 insertions, 1 deletions
diff --git a/test/tools/git/blame-jump-message/script b/test/tools/git/blame-jump-message/script
index 92b1f670..daf5e48c 100644
--- a/test/tools/git/blame-jump-message/script
+++ b/test/tools/git/blame-jump-message/script
@@ -1,5 +1,5 @@
expected_subject=$(cat <<'EOF'
-2017-07-14 A U Thor "Don't break on single quotes or unbalanced {"
+2017-07-13 A U Thor "Don't break on single quotes or unbalanced {"
EOF
)
expected_subject_json=\"$(printf '%s' "$expected_subject" | sed 's/"/\\"/g')\"