3 ms·
> the underlying committed data is always there That’s not always true, due to reflog expiration and GC. This is an important difference to e.g. Subversion wh
by layer8 4y ago
> the underlying committed data is always there
That’s not always true, due to reflog expiration and GC.
This is an important difference to e.g. Subversion where you can delete branches/tags just to hide them, but the history always remains 100% there and nothing is ever really deleted.
- SahAssar 4y agoIn git if a commit is within the history of a branch or tag it won't be GC:ed, right?
- layer8 4y agoThat’s correct, but commits from that history can also be removed, for example by squashing a branch. The Git history is quite mutable in that sense and doesn’t necessarily reflect the actual commit history.