![]() ![]() ![]() Each project branches and tags are mapped to Git branch and tag references.Projects in Subversion repository are mapped to the Git repositories.For every Subversion repository the following mappings are established and used by SubGit: To synchronize Subversion and Git repositories, SubGit maps entities of one system to those of another. SubGit grants users with a choice of whether to use Git or SubversionĬhapter 3.SubGit uses standard hooks mechanism to keep Subversion and Git repositories synchronized.SubGit creates Git repositories and translates existing Subversion revisions into Git commits.SubGit needs direct access to Subversion repository over filesystem.SubGit grants users with a choice of using either Git or Subversion. Figure 1.2 shows the server with SubGit being installed. After that, SubGit configures Subversion and Git hook scripts so, that changes made in the Subversion repository are instantly translated into Git repository and vice versa. ![]() SubGit creates one or more Git repositories alongside with the existing Subversion repository and translates existing Subversion revisions into Git commits. Figure 1.1 shows a generic outline of the described configuration. Correspondingly, users requests are handled by Apache Web Server, svnserve daemon or sshd daemon which invokes svnserve process. Access to Subversion repository is available over network (with HTTP(s), plain svn or svn over SSH protocols) and over the local file system. Most commonly, SubGit user starts with Subversion repository being configured on the server. This book only covers the case when SubGit is installed into existing Subversion repository. requires direct access to both Subversion and Git repositories over local file system.įor creating a Git mirror of a remote Subversion repository, refer to SubGit Remote Book. SubGit is written in Java and works on the server side, i.e. SubGit is a tool for bidirectional Subversion and Git repositories synchronization.
0 Comments
Leave a Reply. |