Spending $17 million to replace git

[drhowarddrfine]

I'll do it for $9 million.

 

[OpenFreeNet]

I didn't understand what the real problem is with Git?

Modern Git replacements/extenders like Sapling, Jujutsu, Gitbutler usally add to Git these features: you have a stack of commits and you can improve them, iteratively, adding things to commits, splitting or folding them; the way you fix merge conflicts is saved, so when you change the commit history again or receive changes upstream, many merges can be reapplied automatically; the history of changes is saved in a log and you can undo/redo and review what you have changed in the repo, not only in the files.

It is easier having a polite history, because commits (expecially not pushed commits) are more "fluid".

Sapling has very few commands, so the CLI is a lot simplified respect Git.

 

[elephant]

The Atlassian stack works well for me. Most of my interaction is a shell prompt with git while Atlassian's hooks into the git repo do the rest. I wish these people well but don't expect to be shopping for a replacement soon.

 

[doul]

OpenFreeNet ok, thanks for your explanations, I started learning git a year ago, today I use about ten commands, it's enough for me alone. Big teamwork should have more issues.