Tutorial by Examples

You need to create a new local copy of the repository with the command git svn clone SVN_REPO_ROOT_URL [DEST_FOLDER_PATH] -T TRUNK_REPO_PATH -t TAGS_REPO_PATH -b BRANCHES_REPO_PATH If your SVN repository follows the standard layout (trunk, branches, tags folders) you can save some typing: git svn...

The equivalent to git pull is the command git svn rebase This retrieves all the changes from the SVN repository and applies them on top of your local commits in your current branch. You can also use the command git svn fetch to retrieve the changes from the SVN repository and bring them to ...

The command git svn dcommit will create a SVN revision for each of your local git commits. As with SVN, your local git history must be in sync with the latest changes in the SVN repository, so if the command fails, try performing a git svn rebase first.

Just use your local git repository as a normal git repo, with the normal git commands: git add FILE and git checkout -- FILE To stage/unstage a file git commit To save your changes. Those commits will be local and will not be "pushed" to the SVN repo, just like in a normal git reposito...

git does not recognice the concept of folders, it just works with files and their filepaths. This means git does not track empty folders. SVN, however, does. Using git-svn means that, by default, any change you do involving empty folders with git will not be propagated to SVN. Using the --rmdir fl...