summaryrefslogtreecommitdiffstats
path: root/shallow.c
diff options
context:
space:
mode:
authorEric Wong <normalperson@yhbt.net>2008-10-30 07:49:26 +0100
committerEric Wong <normalperson@yhbt.net>2008-11-14 07:33:58 +0100
commit16fc08e2d86dad152194829d21bc55b2ef0c8fb1 (patch)
treec01f6e334915761da40fe41e4cd3ec71ca3c4e16 /shallow.c
parentgit-svn: don't escape tilde ('~') for http(s) URLs (diff)
downloadgit-16fc08e2d86dad152194829d21bc55b2ef0c8fb1.tar.xz
git-16fc08e2d86dad152194829d21bc55b2ef0c8fb1.zip
git-svn: respect i18n.commitencoding config
SVN itself always stores log messages in the repository as UTF-8. git always stores/retrieves everything as raw binary data with no transformations whatsoever. To interact with SVN, we need to encode log messages as UTF-8 before sending them to SVN, as SVN cannot do it for us. When retrieving log messages from SVN, we also need to (attempt to) reencode the UTF-8 log message back to the user-specified commit encoding. Note, handling i18n.logoutputencoding for "git svn log" also needs to be done in a future change. Also, this change only deals with the encoding of commit messages and nothing else (path names, blob content, ...). In-Reply-To: <8b168cfb0810282014r789ac01dnec51824de1078f0@mail.gmail.com> James North <tocapicha@gmail.com> wrote: > Hi, > > I'm using git-svn on a system with ISO-8859-1 encoding. The problem is > when I try to use "git svn dcommit" to send changes to a remote svn > (also ISO-8859-1). > > Seems like git-svn is sending commit messages with utf-8 (just a > guessing...) and they look bad on the remote svn log. E.g. "Ca?\241a > de cami?\243n" > > I have tried using i18n.commitencoding=ISO-8859-1 as suggested by the > warning when doing "git svn dcommit" but messages still are sent with > wrong encoding. Signed-off-by: Eric Wong <normalperson@yhbt.net>
Diffstat (limited to 'shallow.c')
0 files changed, 0 insertions, 0 deletions