3 ms·
I think this sort of thing might become much more tractable if it were possible to visualize a git repo as it actually is - i.e. a directed graph of commits (oc
by somewhereoutth 6y ago
I think this sort of thing might become much more tractable if it were possible to visualize a git repo as it actually is - i.e. a directed graph of commits (occasionally with two parents - a merge commit), with moving labels (branch names) and fixed labels (tag names). Like when you buy a small shrub from the garden centre and it has a label attached to it somewhere.
Pushes and pulls can then be visualized as two such shrubs reconciling themselves.
- nicky0 6y agoInteresting analogy, but as a gardener, I've never encountered the concept of a shrub reconciling itself so I have no idea what this visualization reveals!
- somewhereoutth 6y agoImagine a shrub made of shrub A and shrub B. Parts of the shrub (from the root) are from both, parts are from A only, and parts are from B only. Imagine also the 2 sets of labels from A and B. It would become clear how the push/pull is updating its target shrub, and indeed if and what bits of the 2 shrubs (or their labels) conflict.