aboutsummaryrefslogtreecommitdiff
path: root/t
diff options
context:
space:
mode:
authorAvery Pennarun <apenwarr@gmail.com>2008-06-12 19:10:50 -0400
committerJunio C Hamano <gitster@pobox.com>2008-06-14 11:47:55 -0700
commit328eb9b32f7babfb182bad8655491aa6265e96eb (patch)
treecd93107593add40da0efd94b9ab72910468811d4 /t
parent8e7e6f39b6895b6623dc0f6053818704899f41a6 (diff)
downloadgit-328eb9b32f7babfb182bad8655491aa6265e96eb.tar.gz
git-328eb9b32f7babfb182bad8655491aa6265e96eb.tar.xz
git-svn: don't append extra newlines at the end of commit messages.
In git, all commits end in exactly one newline character. In svn, commits end in zero or more newlines. Thus, when importing commits from svn into git, git-svn always appends two extra newlines to ensure that the git-svn-id: line is separated from the main commit message by at least one blank line. Combined with the terminating newline that's always present in svn commits produced by git, you usually end up with two blank lines instead of one between the commit message and git-svn-id: line, which is undesirable. Instead, let's remove all trailing whitespace from the git commit on the way through to svn. Signed-off-by: Avery Pennarun <apenwarr@gmail.com> Acked-by: Eric Wong <normalperson@yhbt.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't')
0 files changed, 0 insertions, 0 deletions