author | Erik Faye-Lund <kusmabite@googlemail.com> | |
Wed, 3 Mar 2010 20:10:22 +0000 (21:10 +0100) | ||
committer | Eric Wong <normalperson@yhbt.net> | |
Fri, 5 Mar 2010 10:57:57 +0000 (02:57 -0800) | ||
commit | 402e139c7e30eb95312aeafdc1a9e8e8167c14cb | |
tree | bec0fe2d711b8e33f948b8233f9405a0e934a825 | tree | snapshot |
parent | a9f979093dabe8b1c7bf8d67863adc378a8bec45 | commit | diff |
git-svn: support fetch with autocrlf on
Before commit d3c9634e, performing a "git svn rebase" that fetched a
change containing CRLFs corrupted the git-svn meta-data. This was
worked around in d3c9634e by setting core.autocrlf to "false" in the
per-repo config when initing the clone. However, if the config
variable was later changed, the corruption would still occur.
This patch tries to fix it while allowing core.autocrlf to be
enabled, by disabling filters when when hashing.
git-svn is currently the only call-site for hash_and_insert_object
(apart from the test-suite), so changing it should be safe.
Signed-off-by: Erik Faye-Lund <kusmabite@gmail.com>
Acked-by: Eric Wong <normalperson@yhbt.net>
Before commit d3c9634e, performing a "git svn rebase" that fetched a
change containing CRLFs corrupted the git-svn meta-data. This was
worked around in d3c9634e by setting core.autocrlf to "false" in the
per-repo config when initing the clone. However, if the config
variable was later changed, the corruption would still occur.
This patch tries to fix it while allowing core.autocrlf to be
enabled, by disabling filters when when hashing.
git-svn is currently the only call-site for hash_and_insert_object
(apart from the test-suite), so changing it should be safe.
Signed-off-by: Erik Faye-Lund <kusmabite@gmail.com>
Acked-by: Eric Wong <normalperson@yhbt.net>
perl/Git.pm | diff | blob | history |