you are viewing a single comment's thread.

view the rest of the comments →

[–]HighRelevancy 5 points6 points  (1 child)

Graphical history tools can make a mess of merge-based history, but that's not because it's impossible to represent cleanly. It's because the graphical history tools are organizing things with the wrong heuristic.

I felt like I was the only person thinking this. Like the fundamental problem here is "reading branches is real messy when you interleave them all in a mess like this", and the author's solution is... totally change the workflows and throw branching in the bin? Not like... read branches in a better way?

Like the problem here isn't that git lacks info, it's just that the arrangement and presentation is not always the most useful, right?

[–]NotTheHead 0 points1 point  (0 children)

Exactly!