summaryrefslogtreecommitdiff
path: root/t/t4013/diff.diff_--cached
diff options
context:
space:
mode:
authorLibravatar Alexey Shumkin <Alex.Crezoff@gmail.com>2013-06-26 14:19:49 +0400
committerLibravatar Junio C Hamano <gitster@pobox.com>2013-06-26 11:40:27 -0700
commitde6029a2d7734a93a9e27b9c4471862a47dd8123 (patch)
tree2932d4fa44ffdf809c9f85ea109bffdda7183ec1 /t/t4013/diff.diff_--cached
parentt4205 (log-pretty-formats): don't hardcode SHA-1 in expected outputs (diff)
downloadtgif-de6029a2d7734a93a9e27b9c4471862a47dd8123.tar.xz
pretty: Add failing tests: --format output should honor logOutputEncoding
One can set an alias $ git config alias.lg "log --graph --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%cd) %C(bold blue)<%an>%Creset' --abbrev-commit --date=local" to see the log as a pretty tree (like *gitk* but in a terminal). However, log messages written in an encoding i18n.commitEncoding which differs from terminal encoding are shown corrupted even when i18n.logOutputEncoding and terminal encoding are the same (e.g. log messages committed on a Cygwin box with Windows-1251 encoding seen on a Linux box with a UTF-8 encoding and vice versa). To simplify an example we can say the following two commands are expected to give the same output to a terminal: $ git log --oneline --no-color $ git log --pretty=format:'%h %s' However, the former pays attention to i18n.logOutputEncoding configuration, while the latter does not when it formats "%s". The same corruption is true for $ git diff --submodule=log and $ git rev-list --pretty=format:%s HEAD and $ git reset --hard This patch adds failing tests for the next patch that fixes them. Signed-off-by: Alexey Shumkin <Alex.Crezoff@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t4013/diff.diff_--cached')
0 files changed, 0 insertions, 0 deletions