summaryrefslogtreecommitdiff
path: root/git-annotate.perl
diff options
context:
space:
mode:
authorEric Wong <normalperson@yhbt.net>2006-03-03 21:35:48 (GMT)
committerJunio C Hamano <junkio@cox.net>2006-03-03 23:07:12 (GMT)
commitce4c8b24a1efcf155c076d54a7e239251504f669 (patch)
treefcb3abcd0986babee6bc58cb5e63be5c48f03cbe /git-annotate.perl
parentf794c23466c2230b15ebf7ec30e06a390d1832a4 (diff)
downloadgit-ce4c8b24a1efcf155c076d54a7e239251504f669.zip
git-ce4c8b24a1efcf155c076d54a7e239251504f669.tar.gz
git-ce4c8b24a1efcf155c076d54a7e239251504f669.tar.bz2
contrib/git-svn: fix a copied-tree bug in an overzealous assertion
I thought passing --stop-on-copy to svn would save us from all the trouble svn-arch-mirror had with directory (project) copies. I was wrong, there was one thing I overlooked. If a tree was moved from /foo/trunk to /bar/foo/trunk with no other changes in r10, but the last change was done in r5, the Last Changed Rev (from svn info) in /bar/foo/trunk will still be r5, even though the copy in the repository didn't exist until r10. Now, if we ever detect that the Last Changed Rev isn't what we're expecting, we'll run svn diff and only croak if there are differences between them. Signed-off-by: Eric Wong <normalperson@yhbt.net> Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'git-annotate.perl')
0 files changed, 0 insertions, 0 deletions