Jujutsu and Git

Changeset evolution has had a rough time of it, but there are some valid reasons for this:

* It has been publicly labeled as "not ready" for ages, despite large numbers of Google and Facebook engineers using it as a daily driver.
* It is yoked to Mercurial, and was only introduced after they had already lost the format war to Git.
* It changed a bunch of its own terminology around for no clear reason ("unstable" was renamed to "orphaned," "troubled" was renamed to "unstable," etc.).
* It blocks push (by default, overridable with --force) when you have unstable changesets in your repository, so it still treats conflicts as problems rather than data. They're just problems you can defer for a bit instead of problems you have to deal with right now.

Disclaimer: I'm one of those Google engineers who use changeset evolution in Mercurial as a daily driver.