跟踪 Git 分支中的提交
tracking commits in a Git branch
为了理解 Git 个分支，我遇到了以下 cited from this page - toward the bottom、
Because a branch in Git is actually a simple file that contains the 40 character SHA-1 checksum of the commit it points to, branches are cheap to create and destroy.
在我的一个项目的 Git 存储库中，当我打开这个文件 .git\refs\heads\master 时，该文件中唯一的东西是一个 40 个字符的 SHA-1，它验证了上述陈述。
现在下一部分 cited from this page - definition for "branch" 是我有一个问题 -
A "branch" is a line of development. The most recent commit on a branch is referred to as the tip of that branch. The tip of the branch is referenced by a branch head, which moves forward as additional development is done on the branch.
假设在名为 feature-400 的分支中有 12 个提交。它们是通过每个跟踪其父项的提交链接在一起的，还是分支本身以某种方式跟踪此历史记录？
前者，即parent跟踪。
为了理解 Git 个分支，我遇到了以下 cited from this page - toward the bottom、
Because a branch in Git is actually a simple file that contains the 40 character SHA-1 checksum of the commit it points to, branches are cheap to create and destroy.
在我的一个项目的 Git 存储库中，当我打开这个文件 .git\refs\heads\master 时，该文件中唯一的东西是一个 40 个字符的 SHA-1，它验证了上述陈述。
现在下一部分 cited from this page - definition for "branch" 是我有一个问题 -
A "branch" is a line of development. The most recent commit on a branch is referred to as the tip of that branch. The tip of the branch is referenced by a branch head, which moves forward as additional development is done on the branch.
假设在名为 feature-400 的分支中有 12 个提交。它们是通过每个跟踪其父项的提交链接在一起的，还是分支本身以某种方式跟踪此历史记录？
前者，即parent跟踪。