> But the snapshot-model also doesn't really make a lot of sense for merges. It's a snapshot of what then? It's a snapshot of the final result. That's the bea

> But the snapshot-model also doesn't really make a lot of sense for merges. It's a snapshot of what then? It's a snapshot of the final result. That's the beauty of the "commit as snapshot" model: each commit always contains the final result of the commit. It doesn't matter if the commit is a normal commit with a single parent, a merge commit with multiple parents, or even an initial commit with zero parents. It doesn't matter if the parent commits are unavailable (shallow repositories). It doesn't matter if the parent commits have been changed (grafts).