Abstract
Whenever I’m asked about the pros of switching from an older version control systems (VCS), such as CVS or Subversion, to git; I answer with this short statement: git branching model. Once you learn to use it you will ask yourself how on earth did I work without it? Indeed, the way git handles branches sets it high above other (if not all) VCS systems. As a matter of fact, I really believe that this single feature is sufficient reason to switch to git.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Notes
- 1.
Yes, these are local branches, as well. They are local branches that track remote branches.
- 2.
The name of the branch can be different—it is the name of the current branch in the remote repository. That’s why Recipe 5-1 was finished with $ git checkout master. It guarantees that after cloning, repository 05-02 will contain the master branch.
- 3.
The path to the file can be different on your system. On CentOS, for example, it is /usr/libexec/git-core.
- 4.
Files are stored in git database as binary large objects (blobs).
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2013 Włodzimierz Gajda
About this chapter
Cite this chapter
Gajda, W. (2013). Branches. In: Git Recipes. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4302-6104-9_5
Download citation
DOI: https://doi.org/10.1007/978-1-4302-6104-9_5
Published:
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4302-6103-2
Online ISBN: 978-1-4302-6104-9
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books