Git-Svn safety and api usage

I can’t find much on this anywhere, before diving into gitsvn I was wondering how safe it is to use against an SVN repository. I have experimented a little, and had one check in which seemed to fail part way through, but didn’t seem to affect my test repository.

Does git-svn only use the public SVN api? Or does it implement any hacks to get around the api in order to implement any more advanced commit features? Are there any known cases where git-svn can corrupt or otherwise damage an SVN repository when used incorrectly?

  • Git svn clone pulls bad repository
  • How do you fix an SVN 409 Conflict Error
  • Temporarily ignore subversion ignore settings
  • SVN repository content
  • git-svn rebase and dcommit problem
  • When I do “git svn rebase” it fetches the svn author names instead of the git author names
  • TortoiseGit cloned SVN repository is empty
  • Which version control system or platform is the best one for tracking and distributing personal Emacs configurations?
  • One Solution collect form web for “Git-Svn safety and api usage”

    git-svn is safe to use (where “is safe” is defined as: There is never a guarantee that software won’t just blow your house off). It mimics an SVN client and cannot perform server other/magic server actions.

    If you are unsure you can always create a svn repository locally

    svnadmin create ~/svn-repo

    clone it locally

    git svn clone ~/svn-repo

    and then you play around: commit (git svn dcommit), update (git svn rebase), etc.

    Git Baby is a git and github fan, let's start git clone.