We were never talking about branches and tags. I think possibly you don't know what "revision" means?

A commit hash identifies both a patch or a revision, that's my point.

> A commit hash identifies both a patch or a revision, that's my point.

Strictly speaking, no. A commit hash identifies a tree. There is no patch stored, nor is a patch bound into the commit hash in any way. The patch is indirectly implied as the differences between the new commit's tree hash and the preceding commit's tree hash.