From 0a4bea856fe6ddd6420d6d7141b20eed8fe0bd25 Mon Sep 17 00:00:00 2001 From: Johannes Altmanninger Date: Sun, 26 Jan 2025 08:37:12 +0100 Subject: 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 --- test/tools/git/blame-jump-message/script | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'test/tools/git') 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')\" -- cgit v1.2.3