> Sapling's problem is pretty obvious: I would have to get others to use FBs merge stack tool and get that past security approval. You don't have to use Saplin

> Sapling's problem is pretty obvious: I would have to get others to use FBs merge stack tool and get that past security approval. You don't have to use Sapling's integration at all, FWIW. I completely avoided PR functionality when I first started using it, and would just do a branch for every commit (which is what it would do for you, anyway.) I think almost every tool imaginable can do a diff between branches? > for JJ (apparently) I `rebase -b main -d foo` These arguments are backwards. What you want is to flip the -d and -b switches which mean "destination" and "branch" respectively: jj rebase -d main -b whatever-branch-you-want jj git push -b whatever-branch-you-want You don't have to switch to any branches or do anything else to make this work. These two commands will basically work no matter what the state of the tree is. > It feels like the documentation is in the same place that Git was in during the early days Yeah. We've talked about this. It's not great but we have so many things going on right now, nobody has totally taken over documentation. Steve Klabnik's Jujutsu tutorial is very popular and we've even considered asking if we could rewrite our documentation using it, but again, so little time. https://steveklabnik.github.io/jujutsu-tutorial/introduction/introduction.html https://steveklabnik.github.io/jujutsu-tutorial/introduction... (I'm one of the Jujutsu developers, in case it wasn't clear from the last paragraph.)