- Git Essentials(Second Edition)
- Ferdinando Santacroce
- 169字
- 2021-07-02 15:27:08
Branches are movable labels
We have seen in the previous sections how the commits are linked to each other by a parent-and-son relationship: each commit contains a reference to the previous commit.
This means that, for example, to navigate within a repository I cannot start from the first commit and try to go to the next, because a commit has no reference to who comes next, but to who comes first. By staying in our arboreal metaphor, this means that our tree is only navigable from leaves, from the extreme top of a branch, and then down to root-commit.
So, branches are nothing but labels that are on the tip commit, the last one. This commit, our leaf, must always be identified by a label so that its ancestors commits can be reached while browsing within a repository. Otherwise, we should remember for every branch of our repository the hash code of the tip commit, and you can imagine how easy it would be for humans.
- 企業數字化創新引擎:企業級PaaS平臺HZERO
- Python金融大數據分析(第2版)
- Modern Programming: Object Oriented Programming and Best Practices
- Architects of Intelligence
- 大數據營銷:如何讓營銷更具吸引力
- 深度剖析Hadoop HDFS
- 基于Apache CXF構建SOA應用
- 辦公應用與計算思維案例教程
- 大數據數學基礎(Python語言描述)
- SQL Server 2008寶典(第2版)
- Kubernetes快速進階與實戰
- Machine Learning for Mobile
- Scratch Cookbook
- GameMaker Game Programming with GML
- 工業大數據工程:系統、方法與實踐