Julia Evans on Nostr: because we have a bunch of rules and expectations around branches like * commits that ...
because we have a bunch of rules and expectations around branches like
* commits that aren't on a branch are almost impossible to see in git (without the reflog), so why would you put them on a diagram?
* commits that aren't on a branch get GC'd eventually
* having 2 branches that point to the same commit is of course possible but feels redundant in most cases
* having a branch that points at an ancestor of another branch is a bit weird (but more common)
(3/?)
* commits that aren't on a branch are almost impossible to see in git (without the reflog), so why would you put them on a diagram?
* commits that aren't on a branch get GC'd eventually
* having 2 branches that point to the same commit is of course possible but feels redundant in most cases
* having a branch that points at an ancestor of another branch is a bit weird (but more common)
(3/?)