On Tue, 04 Jan 2022 at 06:23, Liliana Marie Prikler <liliana.prik...@gmail.com> wrote:
>> The content can be one file, some files, folders, etc. or Git >> objects as Git commit object or Git tree object or whatever. >> Therefore, Git commit hash only depends on the content itself, i.e., >> Git commit object; as explained by the pointer provided earlier in >> the thread, >> >> <https://git-scm.com/book/en/v2/Git-Internals-Git-Objects> > > At some point in there (you can figure out yourself where), you are > mistakenly equating file hashes and commit hashes, which you make > comparison to other tools which only regard the files as content. One > of them is immutable for all I know, the other is subject to very > observable changes. Incorrect. I quote myself: then, for what my opinion is worth on that matter, my probably wrong understanding of your words is that perhaps you are missing a point about content-addressability. Loop.
