author | Eric Wong <normalperson@yhbt.net> | |
Fri, 11 Aug 2006 11:34:07 +0000 (04:34 -0700) | ||
committer | Junio C Hamano <junkio@cox.net> | |
Fri, 11 Aug 2006 23:16:40 +0000 (16:16 -0700) | ||
commit | 17a10f3709c211769c9fada79bd1608aa64f6080 | |
tree | 15c9b631dbea7ced5e5212d79f1c7c25a87f216d | tree | snapshot |
parent | 5bb1cda5f73988963e7470f3cd75a380751f6d99 | commit | diff |
git-svn: correctly kill keyword expansion without munging EOLs
This bugfix applies to users of the svn command-line client only.
We no longer muck with newlines when killing keyword expansion.
This tended to generate unintended diffs in commits because svn
revert -R would destroy the manual EOL changes we were doing. Of
course, we didn't need the EOL munging in the first place, as
svn seems to do it for us even in the text-base files.
Now we set the mtime and atime the files changed by keyword
expansion killing to avoid triggering a change on svn revert,
which svn still seems to want to do.
Thanks to Seth Falcon for reporting this bug.
Signed-off-by: Eric Wong <normalperson@yhbt.net>
Signed-off-by: Junio C Hamano <junkio@cox.net>
This bugfix applies to users of the svn command-line client only.
We no longer muck with newlines when killing keyword expansion.
This tended to generate unintended diffs in commits because svn
revert -R would destroy the manual EOL changes we were doing. Of
course, we didn't need the EOL munging in the first place, as
svn seems to do it for us even in the text-base files.
Now we set the mtime and atime the files changed by keyword
expansion killing to avoid triggering a change on svn revert,
which svn still seems to want to do.
Thanks to Seth Falcon for reporting this bug.
Signed-off-by: Eric Wong <normalperson@yhbt.net>
Signed-off-by: Junio C Hamano <junkio@cox.net>
git-svn.perl | diff | blob | history |