time to time and switch back to the topic branch to continue working
on it. The entire workflow would be something like::
- $ git checkout -b issue-42 # create and switch to a new branch
+ $ git checkout -b issue-42 # create a new issue branch and switch to it
...edit/test/commit...
$ git checkout v2
$ git pull --rebase origin v2 # update v2 from the upstream
When the topic branch is deleted only the label is removed, commits
are stayed in the database, they are now merged into v2::
- o--o--o--o--o--M--< v2 - it is the mainline branch
+ o--o--o--o--o--M--< v2 - the mainline branch
\ /
- --*--*--* - it is the topic branch, now unnamed
+ --*--*--* - the topic branch, now unnamed
The topic branch is deleted to avoid cluttering branch namespace with
small topic branches. Information on what issue was fixed or what
TODO: anonymous access; git over ssh; gitolite; gitweb; cgit; gitlab.
+http://gitolite.com/gitolite/index.html
+
+https://git.kernel.org/cgit/git/git.git/tree/gitweb
+
+http://git.zx2c4.com/cgit/
From Mercurial to git
=====================