4 ms·
> But the old commit is still in there, pristine, forever. > (Git will eventually throw away lost and unused snapshots, but typically not anything you have us
by stinos 4y ago
> But the old commit is still in there, pristine, forever.
> (Git will eventually throw away lost and unused snapshots, but typically not anything you have used in the last 90 days.)
Without having exlplained what a 'snapshot' is and what 'typically' means, it's pretty unclear whether the first statement is affected by the second, and if it were the first is incorrect, so I feel this clarification should be added to the list of things you want people to know about git.
- dale_glass 4y ago> Without having exlplained what a 'snapshot' A commit is effectively a snapshot of the repository at a given point in time. This is unlike some other revision control systems where a commit is a diff. In git, a commit contains whole files, and the diff is generated if needed. > and what 'typically' means Pretty much everything is configurable, and you can invoke the cleanup process by hand if you really want to. > it's pretty unclear whether the first statement is affected by the second, and if it were the first is incorrect Yes, I think it's incorrect and shouldn't be relied on. Things floating around unconnected to a branch can be removed by git eventually. There's plenty time to fix any mistake, but it's not "forever".
- deleted 4y ago[deleted]
- pjerem 4y agoWell, the Part I have en entire chapter enticing you to read Git From The Bottom Up [0] before continuing. So the author can expect that you know what is a snapshot. [0] : https://jwiegley.github.io/git-from-the-bottom-up/ https://jwiegley.github.io/git-from-the-bottom-up/