projects / git.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 5a990e4) | patch
git-svn: recommend rebase for syncing against an SVN repo
authorEric Wong <normalperson@yhbt.net>
Fri, 25 Aug 2006 19:48:23 +0000 (12:48 -0700)
committerJunio C Hamano <junkio@cox.net>
Sat, 26 Aug 2006 04:26:26 +0000 (21:26 -0700)
commit2e93115ed84901fb8ee8447a1baf37cd8c343d8e
tree897f0e00df4fb047c6ae548cc5b8202b51684c21tree | snapshot
parent5a990e45f920b50aa6b81823120223fb50f56d97commit | diff
git-svn: recommend rebase for syncing against an SVN repo

Does this make sense to other git-svn users out there?

pull can give funky history unless you understand how git-svn works
internally, which users should not be expected to do.

Signed-off-by: Eric Wong <normalperson@yhbt.net>
Signed-off-by: Junio C Hamano <junkio@cox.net>
Documentation/git-svn.txt diff | blob | history
Git—the stupid content tracker