| commit | 3ac31e4451ff7c77c7ecbd639e685995e6a8dcc7 | |
| author | Alexander Gavrilov <angavrilov@gmail.com> | |
| Sat, 6 Dec 2008 17:24:35 +0000 (6 20:24 +0300) | ||
| committer | Shawn O. Pearce <spearce@spearce.org> | |
| Mon, 8 Dec 2008 16:33:05 +0000 (8 08:33 -0800) | ||
| tree | bbf9ca451847e9e10bfa676dec34da6b0941d19a | treesnapshot (tar.gz zip) |
| parent | 95e706b5ec4d9b6832640c717c98fb4c912b54c5 | commitdiff |
git-gui: Fix commit encoding handling.
Commits without an encoding header are supposed to
be encoded in utf8. While this apparently hasn't always
been the case, currently it is the active convention, so
it is better to follow it; otherwise people who have to
use commitEncoding on their machines are unable to read
utf-8 commits made by others.
I also think that it is preferrable to display the warning
about an unsupported value of commitEncoding more prominently,
because this condition may lead to surprising behavior and,
eventually, to loss of data.
Signed-off-by: Alexander Gavrilov <angavrilov@gmail.com>
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Commits without an encoding header are supposed to
be encoded in utf8. While this apparently hasn't always
been the case, currently it is the active convention, so
it is better to follow it; otherwise people who have to
use commitEncoding on their machines are unable to read
utf-8 commits made by others.
I also think that it is preferrable to display the warning
about an unsupported value of commitEncoding more prominently,
because this condition may lead to surprising behavior and,
eventually, to loss of data.
Signed-off-by: Alexander Gavrilov <angavrilov@gmail.com>
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
| lib/blame.tcl | diffblobblamehistory | |
| lib/commit.tcl | diffblobblamehistory |