I agree with you, just want to explain what a history is. A "history" is what other version control systems call a "branch." It's the commit and all of its anc

I agree with you, just want to explain what a history is. A "history" is what other version control systems call a "branch." It's the commit and all of its ancestors. Some people think of things this way because the commit ID does depend on its ancestors by depending on its parent (which depends on its parent, which depends on its parent...). This is why, if you rebase a commit, and the content ends up exactly the same (maybe someone already made the equivalent change in both branches), the commit ID still changes: the parent has changed, so the hash changes, so the ID changes. I hope that makes sense.