I don't look at it as either. I simply look at it as a change in code at a location. The commit ID of that change in the history chain is calculated based on

I don't look at it as either. I simply look at it as a change in code at a location. The commit ID of that change in the history chain is calculated based on the commit ID before it and the one before that is calculated based on the one before that all the way down to the very first commit. (Similar conceptually to blockchain) So if you rebase or cherry pick or anything you will be building on top of a new commit ID so git will calculate a new commit ID for your new commit even though the code change is the same. It's pretty simple... if you understand that concept you can get 90% of the way there with git.