Page History

At the average, translation of one revision translation takes 1-1.5 seconds. Of course, the bigger the number of the revision is, the longer is the translation. If it runs much slower, though, there are few things to consider:

• most often, slow translations is caused by incorrect branches and tags mapping configuration. The most recommended way to create correct configuration is to useuse ‘subgit configure’with with ‘layout auto’option option:

  Code Block
  theme FadeToGrey
  $ subgit configure --layout auto --trunk TRUNK_PATH SVN_PROJECT_URL [GIT_REPO_PATH]

  where

  • TRUNK_PATH - a path, relative to the SVN_PROJECT_URL, that leads to the directory playing a role of ‘trunk’ or ‘main line’ of development in the SVN project.
  • SVN_PROJECT_URL - a URL that points to a single project in SVN repository, that’s intended to be translated to Git.
  • GIT_REPO_PATH - an optional path to a new Git repository, where the SVN project will be translated to.

  As an example, the command may look like this:

  Code Block
  theme FadeToGrey
  $ subgit configure --layout auto --trunk main http://example.com/svn/repository/project /home/user/project.git

  SubGit will connect to the SVN project, scan its history and based on the TRUNK_PATH will try to find appropriate branches and tags and create valid mapping configuration.

  In rare occasions, though, the SVN project history and layout are so complex SubGit cannot create correct mapping configuration. In these cases the only way to set the mapping scheme is to create it manually following the mapping guide:

  BRANCHES AND TAGS MAPPING

  Another reason to change the mapping scheme manually is to exclude some branches, tags or particular files from the translation if they are not worth to be translated to Git. It can also speed up the translation, as the fewer branches and tags are in a mapping, the fewer revisions and data to translate.

...