3 ms·

https://github.blog/2020-12-17-commits-are-snapshots-not-diffs/ https://github.blog/2020-12-17-commits-are-snapshots-not-dif... (I don't necessarily agree with

https://github.blog/2020-12-17-commits-are-snapshots-not-diffs/ https://github.blog/2020-12-17-commits-are-snapshots-not-dif... (I don't necessarily agree with the article's messaging around "Haha you were only confused by git because you thought commits are diffs now that you know they're actually snapshots you have no more confusion", because, as the article itself admits, most of the commands like cherry-pick do work on dynamically-computed diffs anyway.)

brabel 5y ago
Interesting... a git commit is almost always represented as a diff... example: https://github.com/github/gitignore/commit/991e760c1c6d50fdda246e0178b9c58b06770b90.patch https://github.com/github/gitignore/commit/991e760c1c6d50fdd... Whether it's represeented as a diff internally seems completely irrelevant to me, even to understand the examples in the article. I would like to be able to "de-serialize" a real commit's data to see exactly what's stored, but this article doesn't seem to show how to do that... do you have a suggestion on how to do that?