The only version management that i find intuitive is wiki model(i.e. wiki articles).
Imagine 3 tasks.
1.Revert 3 git commits. This is one-click revert in wiki.
2.Diff 2 arbitrary commits. One-click in wiki.
3.change 2 lines of code. Edit->Submit in wiki.
Why git has to be so arcane, especially
reverting to specific point in time?
The first code versioning control system that emulates the wikipedia UI model will win the market.
1.Revert 3 git commits. This is one-click revert in wiki.
2.Diff 2 arbitrary commits. One-click in wiki.
3.change 2 lines of code. Edit->Submit in wiki.
Why git has to be so arcane, especially reverting to specific point in time? The first code versioning control system that emulates the wikipedia UI model will win the market.