Skip to content

Commit

Permalink
docs: update Sapling comparison logs
Browse files Browse the repository at this point in the history
  • Loading branch information
AngelEzquerra authored and PhilipMetzger committed Feb 1, 2025
1 parent 7e55dd2 commit 7c74866
Showing 1 changed file with 4 additions and 5 deletions.
9 changes: 4 additions & 5 deletions docs/sapling-comparison.md
Original file line number Diff line number Diff line change
Expand Up @@ -60,11 +60,10 @@ Here is a list of some differences between jj and Sapling.
* **Git interop:** Sapling supports cloning, pushing, and pulling from a remote
Git repo. jj also does, and it also supports sharing a working copy with a Git
repo, so you can use `jj` and `git` interchangeably in the same repo.
* **Polish:** Sapling is much more polished and feature-complete. For example,
jj has no `blame/annotate` or `bisect` commands, and also no copy/rename
support. Sapling also has very nice web UI
called [Interactive Smartlog](https://sapling-scm.com/docs/addons/isl), which
lets you drag and drop commits to rebase them, among other things.
* **Polish:** Sapling is more polished and feature-complete. For example, jj
has no `bisect` command. Sapling also has very nice built-in web UI called
[Interactive Smartlog](https://sapling-scm.com/docs/addons/isl), which lets
you drag and drop commits to rebase them, among other things.
* **Forge workflow:** Sapling has `sl pr submit --stack`, which lets you
push a stack of commits as separate GitHub PRs, including setting the base
branch. It only supports GitHub. jj doesn't have any direct integration with
Expand Down

0 comments on commit 7c74866

Please sign in to comment.