Branches mapping overview.
Branches mapping is a set of rules that establish a correspondence between SVN and Git branches and tags. These rules are defined by branches mapping configuration options in SubGit configuration file.
Branches and Tags in Subversion.
There are few key Subversion concepts, that matter in the context of SubGit mapping process:
- repository – a central store, root directory, that holds all data in the form of a filesystem tree. A repository contains one or more projects.
- project – a data part in a repository, that can be logically distinguished from the rest, like a distinct software product or a library. Most projects have their own recognizable "main lines" and "divergent copies" of development.
- branch - a distinct line of development that exists independently of all others, yet still shares a common history. A branch is a directory within repository or project, which contains all files of that particular line of development.
- tag – a named snapshot of a development line in time. A tag is also a directory within repository or project. The main difference between branch and tag is that tags are supposed to be unchanged with time.
- trunk – a branch, that represents the main line of development. It's a directory within repository or project, which contains the main line of development.
- revision – a certain state of the filesystem tree, that has an assigned number and commentary.
- layout – a way how repository or project filesystem tree is organized.
- standard layout – a repository layout, that Subversion development team recommends to follow. According to that layout, each project resides in its own subdirectory within a repository and has three subdirectories for trunk, branches and tags.
A SVN repository can be organized in any way and SubGit can deal with any possible SVN repository layout.
A graphical representation of the explained SVN concepts:
