What are your version control pain points?

Question

Whether it's git or hg or p4... what do you wish your VCS could do differently? Do you feel constrained by size or scale? Do you wish it were less sluggish? More flexible or easy to use? Easier to customize for your team's processes or workflows?To give one example, I've worked at multiple companies where the codebase was split across many git repos, and the slew of repos made everything harder to coordinate, develop, and understand. Maybe this resonates with you -- or maybe you have other problems?(Context: I build developer tools, including currently a VCS. Nothing is more compelling to me than the day-to-day struggles of a developer who just wants to ship their code, god damn it.)

elviejo · Accepted Answer

I want a VCS that treats code as an AST not as text because: That way meaningless white-space changes, wouldn't cause a diff. Renaming a function would be just that a rename, not a 100 lines with + and -. Where every commit is recorded (ala Fossil)... but where a set of commits can be seen as if was just one. (So that a meaningful set can be seen as what it was).