4 ms·
Correct -- I was being terse: the commit is a function of the changes going in (and metadata like time, authorship). Details: https://gist.github.com/masak/241
by anilgulecha 10y ago
Correct -- I was being terse: the commit is a function of the changes going in (and metadata like time, authorship).
Details: https://gist.github.com/masak/2415865 https://gist.github.com/masak/2415865
- 0x0 10y agoI'm not really talking about entire git commits, but just single files (blobs) within any commit/tree/repository
- chronial 10y agoThat is not correct and also not supported by your link. A git commit does not contain any changes. It is always a full sapshot of the repo state. To have any kind of concept of "change", you need two gït commits. Just like a simple text file.