Git, Jujutsu, Sapling, GitButler or Mercurial for a small local code project
Git is the safe choice when someone else will receive your project. Jujutsu is the alternative to consider if you rewrite your own history often and can live within its Git limits.
Git
The format every colleague and code host reads, with interactive rebase, revert and reflog for editing and undoing local history.
Rebases stop at each conflict and reflog entries expire. Keep Git updated: a July 2025 flaw has been exploited in attacks.
Why Git is our PickTeam behind Git? Get your award badge
No Rising Star selected
Jujutsu first shipped in March 2022, so it is older than our two-year window for newer entrants. The newer Git-compatible tools we found are not yet ready for this job.
We did not find a tool released in the past two years that edits earlier commits and hands a project to another developer.
Who is this article for? Solo developers choosing a local version-control CLI to revise history, recover a mistake and hand a small project to another developer.
About 25 min read
What Preferred Pick, Rising Star and Ready to Rock mean
The quick list
Git, Jujutsu, Mercurial and GitButler are free, and we could not confirm Sapling’s price. Choose by what the person receiving your project uses and how often you rewrite your own history.
Git, Jujutsu and Mercurial are free, open-source command-line tools with no account or subscription, checked October 19 and November 12, 2026. Licences: GPLv2 for Git, Apache 2.0 for Jujutsu, GPLv2 or later for Mercurial. GitButler is free under a source-available licence, and we could not confirm Sapling’s price. Hosting, backup and support costs are separate.
The comparison at a glance
Compare how each tool edits and undoes history, how it hands a project to another developer, and its 2026 maintenance and security record.
Order follows our verdict for a small local project handed to another developer, not popularity or speed. All tools remain selectable.
Hides matching answers for the selected tools. Unknowns and unverified claims stay visible.
| Feature | Git | Jujutsu | Sapling | GitButler | Mercurial |
|---|---|---|---|---|---|
| Best fit | Handing the project to another developer, who almost certainly uses Git | Rewriting your own local history often in a Git-backed project | Working in a Git repository with stacks of commits and Sapling’s own commands | Parallel branches and commit editing in a Git repository, with a managed workspace branch | Collaborators who already use Mercurial |
| Cost and licence | $0; GPLv2; Software Freedom Conservancy member project | $0; Apache 2.0; community-maintained | Not confirmed: no price or licence text on the pages read | $0; source-available under the Functional Source License 1.1 | $0; GPLv2 or later |
| Editing an earlier commit | Interactive rebase; stops at each conflict until you resolve or abort. Experimental git history command for simple single-commit edits | Edit any change; later changes rebase automatically and conflicts are recorded instead of stopping the command | histedit, amend --to, absorb, drop, uncommit and rebase (which stops at a conflict until you continue it) | Edit commits and resolve conflicts from the command line; operations log restores older states | histedit extension, shipped but switched off by default; stops at each conflict |
| Undoing a mistake | revert adds an inverse commit; reflog keeps old branch positions (unreachable entries expire after 30 days by default) | Operation log: undo the last operation, revert a specific one or restore an earlier state | No undo command documented on the pages read | Operations log with restoration of older states | backout adds an inverse changeset |
| Handoff to another developer | Native: clone, bundle or push to any Git host | Git repository underneath; resolve conflicts first, or a Git user sees .jjconflict folders | Ordinary Git repository in .git mode; mixing sl and git commands might not work in all cases | Git-backed; work lives on a managed gitbutler/workspace branch | Native for Mercurial users; Git users need hg-git or the bundled experimental git extension |
| Security record | July 2025 submodule flaw (CVE-2025-48384) exploited in attacks; fixed in 2.50.1 and in patch releases back to 2.43.7. A High-rated clone flaw with submodules (CVE-2026-111760, November 2026) is fixed in 2.56.1. Git for Windows: six advisories since March 2026 | Three advisories, all fixed: critical path traversal via crafted Git repositories (0.23.0, 2024), branch-name injection, SHA-1 collision detection (0.28.1, 2025) | No advisory list or adverse-report search read | An October release fixed commands that deleted tracked files; no advisory list read | No Mercurial vulnerability disclosed after 2019 in OSV |
| Reader reviews | No reviews yet. Write a review | No reviews yet. Write a review | No reviews yet. | No reviews yet. | No reviews yet. Write a review |
These are command-line tools; all but Sapling have a confirmed price of $0. None of these sources measures speed, failure rates or behaviour with remote collaborators. Resolve Jujutsu conflicts before handing a repository to a Git user, and keep whichever tool you use updated. Facts checked October 19, 2026; releases, advisories and prices rechecked November 12, 2026.
All features and sources 11 criteria
Open the groups that matter to you. They compare the same selected tools. “Planned” means future work, not an available feature. Sources include the published conditions.
Editing and undoing history
Show 2 criteria
| Feature | Git | Jujutsu | Sapling | GitButler | Mercurial |
|---|---|---|---|---|---|
| Editing an earlier commit | Interactive rebase; stops at each conflict until you resolve or abort. Experimental git history command for simple single-commit edits | Edit any change; later changes rebase automatically and conflicts are recorded instead of stopping the command | histedit, amend --to, absorb, drop, uncommit and rebase (which stops at a conflict until you continue it) | Edit commits and resolve conflicts from the command line; operations log restores older states | histedit extension, shipped but switched off by default; stops at each conflict |
| Undoing a mistake | revert adds an inverse commit; reflog keeps old branch positions (unreachable entries expire after 30 days by default) | Operation log: undo the last operation, revert a specific one or restore an earlier state | No undo command documented on the pages read | Operations log with restoration of older states | backout adds an inverse changeset |
These selected tools have matching answers in this group. Turn off “Show differences only” to see them.
Sources for editing and undoing history
Documentation read October 19, 2026: Git rebase, revert, reflog and git history; Jujutsu operation log; Mercurial histedit and backout. Sapling’s amend and undo commands were not read. Documented behaviour, not measured reliability.
Handoff and compatibility
Show 3 criteria
| Feature | Git | Jujutsu | Sapling | GitButler | Mercurial |
|---|---|---|---|---|---|
| Handoff to another developer | Native: clone, bundle or push to any Git host | Git repository underneath; resolve conflicts first, or a Git user sees .jjconflict folders | Ordinary Git repository in .git mode; mixing sl and git commands might not work in all cases | Git-backed; work lives on a managed gitbutler/workspace branch | Native for Mercurial users; Git users need hg-git or the bundled experimental git extension |
| Git features not supported | None; this is Git | Hooks, .gitattributes and Git LFS; submodules kept but hidden from the working copy; partial tag and config support | Git LFS and .gitattributes partly supported; no local tags; submodules not fully supported | Warning against editing or resolving commits in Git LFS or git-crypt repositories | Git features apply only through an extension |
| Install | Preinstalled or packaged on almost every system | Prebuilt binaries for Windows, macOS and Linux; needs Git 2.42.0 or later | Homebrew on macOS, a ZIP you unpack on Windows, Linux packages | Installs from its desktop client or with a one-line install script; macOS, Windows and Linux | Packages for Windows, macOS, Linux and BSD; Python 3.9 or later |
These selected tools have matching answers in this group. Turn off “Show differences only” to see them.
Sources for handoff and compatibility
Read October 19, 2026: Jujutsu Git compatibility and installation; Mercurial clone, downloads and the hg-git package; About Git.
Maintenance, security and stewardship
Show 5 criteria
| Feature | Git | Jujutsu | Sapling | GitButler | Mercurial |
|---|---|---|---|---|---|
| Cost and licence | $0; GPLv2; Software Freedom Conservancy member project | $0; Apache 2.0; community-maintained | Not confirmed: no price or licence text on the pages read | $0; source-available under the Functional Source License 1.1 | $0; GPLv2 or later |
| Current release, checked November 12, 2026 | 2.56.1, a security release; Git for Windows 2.56.1.windows.1, November 10 | 0.47.1, November 5, 2026; monthly releases, before 1.0 | 0.2.20261103, November 3, 2026 | 0.23.4, November 10, 2026; frequent 0.x releases | 7.2.4, August 11, 2026 |
| Change to plan for | Git 3.0 will default new repositories to SHA-256 and main and require Rust to build; no release date set | The README warns of workflow and on-disk format changes before 1.0; 0.46.0 lists seven breaking changes and 0.47.0 more | Version 0.2.x; Git mode is one of two modes and is not the maker’s main use | Client being rewritten: an October 28 commit retires one client | Shrinking ecosystem: Mozilla moved Firefox from Mercurial to Git in April 2025 |
| Security record | July 2025 submodule flaw (CVE-2025-48384) exploited in attacks; fixed in 2.50.1 and in patch releases back to 2.43.7. A High-rated clone flaw with submodules (CVE-2026-111760, November 2026) is fixed in 2.56.1. Git for Windows: six advisories since March 2026 | Three advisories, all fixed: critical path traversal via crafted Git repositories (0.23.0, 2024), branch-name injection, SHA-1 collision detection (0.28.1, 2025) | No advisory list or adverse-report search read | An October release fixed commands that deleted tracked files; no advisory list read | No Mercurial vulnerability disclosed after 2019 in OSV |
| Who maintains it | The Git project, a Software Freedom Conservancy member | Nine elected maintainers; at most a third may be paid by one company. Creator joined start-up ERSC as CTO in September 2026 | Meta | GitButler, a company; source opened in February 2024 | The Mercurial community |
These selected tools have matching answers in this group. Turn off “Show differences only” to see them.
Sources for maintenance, security and stewardship
Read October 19 and November 12, 2026: Git downloads, November 2026 Git advisory, planned breaking changes, Git and Git for Windows advisories, CISA exploited-vulnerabilities catalog; Jujutsu README, Sapling Git support modes and installation (November 12, 2026), GitButler CLI overview and releases (November 12, 2026), 0.46.0 release, governance, path traversal advisory and ERSC announcement; Mercurial 7.2.4 and DevClass on Mozilla.
Earlier hands-on check, October 1, 2026
Show 1 criteria
| Feature | Git | Jujutsu | Sapling | GitButler | Mercurial |
|---|---|---|---|---|---|
| Earlier hands-on check, October 1, 2026 (historical) | 2.43.0 and a separate 2.56.0 build: earlier edit kept after conflict resolution; revert and reflog recovery; clones matched | 0.45.1: operation-log recovery; resolved handoff matched in Git; unresolved handoff showed conflict folders | No hands-on check | No hands-on check | 7.2.4: histedit after conflict resolution; backout; Mercurial clone matched |
These selected tools have matching answers in this group. Turn off “Show differences only” to see them.
Sources for earlier hands-on check, october 1, 2026
Historical observation from a small Linux check run on October 1, 2026, before Practical Picks adopted its research-only method on October 3. It used one synthetic three-line text file and did not decide any recommendation. Upstream Git 2.43.0 falls within the affected range of CVE-2025-48384; the record does not show whether that system’s package carried the distribution’s backported fix. Earlier check record, October 1, 2026.
What matters when choosing
Git is our Preferred Pick for a solo developer who will hand a small project’s history to another developer. Whoever receives the project almost certainly has Git, and every code host and editor reads its repositories, so the handoff needs no conversion. It has the tools this job needs: an interactive rebase to change an earlier commit, git revert to undo a committed mistake with a new commit, and a reflog that remembers where your branches pointed before. The current release is 2.56.1, a security release that fixes six CVEs, including one rated High (CVE-2026-111760); we did not read the other five severities. Git is free under the GPLv2. The compromises are real. A rebase stops at every conflict until you resolve it or give up, and the reflog is a time-limited safety net: entries for commits that no branch reaches any more expire after 30 days by default. Keep Git up to date. A flaw published in July 2025 (CVE-2025-48384) lets a repository with a crafted submodule run a script when you clone it with its submodules, and the US Cybersecurity and Infrastructure Security Agency lists it as exploited in attacks. A similar flaw in clones with submodules (CVE-2026-111760, rated High) was published in November 2026 and is fixed in 2.56.1. Git downloads, rebase, reflog, CVE-2025-48384 advisory
Jujutsu is the one to consider for developers who rewrite their own local history often and can work within its Git limits. Its first GitHub release came in March 2022, so it is older than the two-year window we use for newer entrants, and we name no Rising Star in this comparison. It keeps your project in an ordinary Git repository, but it records every operation in a log you can undo, and when you change an earlier commit it moves the later ones on top automatically, recording any conflict instead of stopping. Those features are documented, and an independent LWN.net review described them. The limits matter for a handoff: a commit with an unresolved conflict does not translate into Git, so the recipient sees conflict folders instead of your file; Git hooks, .gitattributes and Git LFS are not supported; and its monthly releases often include breaking changes. Its creator left Google in September 2026 to become chief technology officer of East River Source Control, a start-up. The project stays under the Apache 2.0 licence and elected maintainers, no more than a third of whom may be paid by one company. Project, operation log, Git compatibility, governance
Sapling and GitButler also scored well, but we do not name either as our pick. Sapling, from Meta, works inside an ordinary Git repository and handles rebases and stacks of commits, but its own documentation says that mixing its commands with Git’s might not work in every case, and that Git LFS, .gitattributes, local tags and submodules are only partly supported. GitButler’s command-line tool is free, edits commits, keeps an operations log and works on Git repositories, but it keeps your work on a branch of its own and warns against editing commits in repositories that use Git LFS or git-crypt. Neither first appeared within our two-year window for newer entrants. Jujutsu, Sapling and GitButler finished within a tenth of a point of one another, so we list them without ranking them against each other. Sapling Git modes, GitButler CLI
Choose Mercurial when the people you hand the project to already use it. It is maintained (7.2.4, August 11, 2026), free under the GPLv2 or later, and its shipped histedit extension and backout command cover editing and undoing. Handing a Mercurial project to a Git user needs an extra extension, though, and its ecosystem is shrinking: Mozilla moved Firefox’s source of truth from Mercurial to Git in April 2025. About Mercurial, histedit, hg-git, DevClass on Mozilla
Git
Preferred Pick · handoff to another developer
Choose Git when the person receiving your project expects an ordinary Git repository, which is almost everyone. Keep it updated, and finish or abort each rebase before you hand the project over.
Reasons to choose it
- The native format for every code host, editor and colleague
- Interactive rebase, revert and reflog cover editing and undoing
- Mature release and security process; 2.56.0 arrived September 28, 2026
What to watch
- A rebase stops at each conflict until you resolve or abort it
- Reflog entries for unreachable commits expire after 30 days by default
- A July 2025 flaw has been exploited in attacks; run a fixed release
Git’s interactive rebase lets you stop at an earlier commit, change it, and replay the later commits on top. When a later commit touches the same lines, the replay stops until you resolve the conflict and continue, or abort and return to where you started. To undo a mistake that is already committed, git revert adds a commit that reverses it and leaves both in the history, which is the safe choice once anyone else has a copy. If you move a branch by accident, the reflog records where it pointed before, but its entries expire: after 90 days by default, or 30 days for commits that no branch reaches any more. Since version 2.54, Git also has an experimental git history command that rewords, splits, fixes up or drops one earlier commit without an interactive rebase. Its documentation says it does not yet handle merges, refuses edits that would cause conflicts, and may change. Rebase, revert, reflog, git history
Handoff is where Git is strongest. A clone, a bundle or a push to any host gives the recipient the same repository you have, with no conversion. Git is free under the GPLv2 and is a member project of the Software Freedom Conservancy. Feature releases arrive every two to three months: 2.54.0 in April 2026, 2.55.0 in June and 2.56.0 on September 28. Version 2.56.1 is a security release, and Git for Windows 2.56.1.windows.1 followed on November 10. Git 3.0 will make new repositories use SHA-256 and a main branch by default and will require Rust to build Git, but the project has set no release date. About Git, 2.56 release notes, planned breaking changes
Read the full Git analysis and sources
Security fixes come in coordinated releases that also patch older versions. The most serious recent flaw, published July 8, 2025, lets a repository with a crafted submodule path run a script during checkout. It is fixed in 2.43.7, 2.44.4, 2.45.4, 2.46.4, 2.47.3, 2.48.2, 2.49.1, 2.50.1 and later releases, and CISA added it to its catalog of exploited vulnerabilities on August 25, 2025. On November 10, 2026 Git published a High-rated advisory (CVE-2026-111760) for a similar flaw: cloning an attacker-controlled repository with --recurse-submodules can run code. Version 2.56.1 and patch releases for 2.50 to 2.55 fix it along with five other flaws, though the advisory page itself still lists no patched version. Git for Windows publishes its own advisories and has published six since March 2026, including two flaws that could leak a Windows password hash when you clone from a malicious server (fixed in 2.53.0 builds) and a bundle-address flaw from August 2026 whose page lists no fixed version but whose affected ranges end before the 2.55.0.windows.4 build, so current builds are outside it. Linux distributions often patch without changing the version number: Ubuntu 24.04’s Git still reports 2.43.0 after its July 2025 fix. Check your system’s security notices, not only git --version. Advisory list, November 2026 advisory, CISA catalog, Git for Windows advisories, Ubuntu notice
In an earlier hands-on check on October 1, 2026, before we adopted our research-only method, a Linux system’s Git 2.43.0 worked through a three-line text file. An interactive rebase changed an earlier commit; replaying a later edit to the next line stopped at a conflict, and once it was resolved both changes survived. A later edit in a separate file replayed without conflict. git revert reversed a deliberate bad commit, and separate clones received the expected file byte for byte. A separately built Git 2.56.0 restored a displaced branch tip from the reflog. Upstream 2.43.0 is inside CVE-2025-48384’s affected range, and the record does not show whether that system’s package carried its distribution’s fix, so read that run as a dated observation, not a version to use. It did not cover remote pushes, hooks, large repositories or security. Earlier check record, October 1, 2026
Used Git? Share your experience to help other readers choose.
Jujutsu
Close alternative · frequent local history edits
Consider Jujutsu if you rewrite your own commits often and your project does not need Git hooks, LFS or submodules. Resolve every conflict before you hand the repository to a Git user, and keep a Git backup of anything important.
Reasons to choose it
- Any operation can be undone from the operation log
- Editing an earlier commit rebases the later ones automatically
- Keeps the project in a Git repository you can push to any host
What to watch
- Unresolved conflicts reach Git users as conflict folders
- No Git hooks, .gitattributes or LFS; submodules hidden
- Before 1.0: monthly releases often include breaking changes
Jujutsu (the command is jj) treats your working copy as a commit and records every command that changes the repository in an operation log. jj undo steps back one operation at a time, jj op revert reverses a specific earlier operation, and jj op restore returns the whole repository to an earlier state. When you change an earlier commit, the later ones are rebased automatically, and a conflict is stored in the commit for you to resolve later instead of halting the command. LWN.net’s January 2024 review summed up the difference from Git: “Unlike the reflog, the operation log treats rebases or other complex operations as single atomic entries.” Operation log, LWN.net review
Your project lives in a Git repository, which you can share by pushing a bookmark (Jujutsu’s name for a branch) to any Git host or by letting a colleague clone it. Jujutsu’s compatibility page sets out the limits. “Commits with conflicts cannot be represented in Git”: the recipient sees .jjconflict-base-* and .jjconflict-side-* folders instead of the file. Hooks, .gitattributes and Git LFS are not supported, submodules are kept but do not appear in the working copy, and only some Git configuration is respected. Jujutsu also needs Git 2.42.0 or later installed. If your project depends on hooks, LFS or submodules, stay with Git. Git compatibility, installation
Read the full Jujutsu analysis and sources
It is young and says so. Its README calls it “an experimental version control system” and warns of “backward-incompatible changes to the on-disk formats before version 1.0.0”. It ships monthly; 0.46.0, from October 7, 2026, lists seven breaking changes, and 0.47.0, from November 4, lists more. Version 0.47.1 followed on November 5. It has had three security advisories, all fixed: a critical flaw that let a crafted Git repository make jj write files outside the clone (fixed in 0.23.0, November 2024), a low-severity branch-name injection (0.26.0, February 2025) and missing SHA-1 collision detection (0.28.1, April 2025). Its issue tracker also holds 2026 reports of damaged repositories: a data-integrity bug in how jj stores some of its own metadata, reported in June and fixed in August, and an open, unreproduced report of a repository left unusable after jj git fetch. These are individual reports, not failure rates, but keep a Git backup of anything important. README, 0.46.0 release, path traversal advisory, issue 9649, issue 8511
Martin von Zweigbergk started Jujutsu as a hobby project in late 2019 and developed it at Google; the project’s README says it is “not a supported Google product”. On September 1, 2026, he joined East River Source Control as chief technology officer. The start-up says it is backed by Amplify Partners and is building version-control storage; the announcement says he remains a core maintainer and that Jujutsu stays Apache 2.0. Contributors sign Google’s contributor licence agreement, and nine elected maintainers direct the project under governance rules that let no single company pay more than a third of them. Its first GitHub release, 0.3.0, came on March 13, 2022. Its first release is still more than two years old, which is why it is not our Rising Star. ERSC announcement, governance, first release
In an earlier hands-on check on October 1, 2026, before we adopted our research-only method, Jujutsu 0.45.1 edited an earlier change in a Git-backed repository and presented the conflict with the later edit for resolution; a later edit in a separate file needed none. After a deliberate mistaken jj restore, jj op revert brought the lost line back. Once the conflict was resolved, a bookmark cloned into ordinary Git with the expected file. A bookmark on the unresolved conflict did not: the Git copy held .jjconflict-* folders and a notes.txt missing the later line, as the documentation predicts. Resolve conflicts with Jujutsu before any Git handoff, and check the recipient’s copy. Earlier check record, October 1, 2026
Used Jujutsu? Share your experience to help other readers choose.
Sapling
Close alternative · stacked commits in a Git repository
Consider Sapling if you like working with stacks of commits and will use its commands, not Git’s, inside the repository. Keep to one set of commands, and check Git LFS, attributes and submodules before handing a project over.
Reasons to choose it
- Works in an ordinary Git repository in its Git mode
- histedit, amend --to, absorb, drop and uncommit, plus stacked commits
- Builds for macOS, Windows and Linux
What to watch
- Mixing its commands with Git’s might not work in every case
- Git LFS, attributes and submodules only partly supported
- We could not read its price, and the pages we read documented no undo command
Sapling is Meta’s source-control client. Its .git mode works on a repository created with git clone or git init, and the maker’s pages say Git commands still run there. It has its own sl rebase, which like Git’s must be continued with sl rebase --continue after an interruption, and it tracks stacks of commits without a staging area. Its release notes list histedit, amend --to, absorb, drop and uncommit for changing earlier commits. The pages we read documented no undo command, so we cannot say how it recovers from a mistake. Builds exist for macOS through Homebrew, for Windows as a ZIP file you unpack yourself, and for Linux; the current build is 0.2.20261103. Git support modes, installation, getting started
The handoff limits come from the maker. Mixing sl and git commands “might not work in all cases”: an interrupted sl rebase has to be continued with sl, and a file added with sl add might not show in git status. sl may leave the repository on a detached head, so create a branch before using git checkout. Git LFS and .gitattributes are only partly supported, there are no local tags, and submodules are “not fully supported”. We found no price, licence text or security advisory list on the pages we read, and we did not search for adverse reports, so treat our score for it as less certain. Git support modes
Used Sapling? Share your experience to help other readers choose.
GitButler
Close alternative · parallel branches in a Git repository
Consider GitButler if you juggle several branches at once and are happy to let it manage a workspace branch. Avoid editing commits with it in repositories that use Git LFS or git-crypt.
Reasons to choose it
- Edits commits and resolves conflicts from the command line
- Operations log can restore older states
- Free, and works on Git repositories
What to watch
- Work lives on a managed workspace branch
- Warns against editing commits where Git LFS or git-crypt is used
- Changes fast; an October release fixed deleted tracked files
GitButler’s command-line tool, but, is part of its client. The maker’s documentation lists branch and stack management, an operations log with restoration of older states, commit editing and conflict resolution, and the project is backed by Git. Its client is free to download on macOS and Windows, with Linux packages, and the command-line tool installs from its desktop client or with a one-line install script; and the project describes itself as free and open source, though the source is released under the Functional Source License rather than an open-source licence. CLI overview, project
The limits are in its own notes. Your work lives on a managed gitbutler/workspace branch; until version 0.23.4, on November 10, 2026, a plain git commit there could break the project. The same notes keep a warning against editing and resolving commits in repositories that use Git LFS or git-crypt. It ships often and has changed fast: an October release fixed commands that deleted tracked files, and an October 28 commit retires one of its clients. GitButler opened its client to the public in February 2024. Its command-line tool is the command-line version of the same product and ships in the same releases, so we count from February 2024. Release notes, Opening Up GitButler
Used GitButler? Share your experience to help other readers choose.
Mercurial
Also consider · collaborators who use Mercurial
Choose Mercurial when the people receiving your project already use it and a Mercurial clone is the handoff they expect.
Reasons to choose it
- histedit and backout cover editing and undoing
- Steady releases; 7.2.4 arrived August 11, 2026
- No Mercurial vulnerability disclosed after 2019, per OSV
What to watch
- histedit must be switched on before first use
- Handing off to Git users needs an extra extension
- A shrinking ecosystem: Mozilla moved Firefox to Git in 2025
Mercurial edits earlier changesets with histedit, an extension that ships with Mercurial but must be switched on, and undoes a committed mistake with hg backout, which adds an inverse changeset. Like Git’s rebase, histedit stops at a conflict until you resolve it and continue, or abort. A plain hg clone hands the full history to anyone who uses Mercurial. histedit, backout, clone
The project is active and steady. Version 7.2 came out on January 29, 2026 and 7.2.4 on August 11; packages exist for Windows, macOS, Linux and BSD; and the OSV vulnerability database lists no Mercurial vulnerability disclosed after 2019. Mercurial is free under the GPLv2 or later. Its weakness for this reader is the handoff to Git users. That needs the third-party hg-git extension, last released in February 2025, or Mercurial’s bundled git extension, which the hg-git documentation says cannot handle every Git repository. The wider ecosystem is also shrinking: Mozilla made Git the source of truth for Firefox on April 30, 2025, after years on Mercurial. Downloads, 7.2.4 release, hg-git, DevClass on Mozilla
Read the full Mercurial analysis and sources
In an earlier hands-on check on October 1, 2026, before we adopted our research-only method, Mercurial 7.2.4’s histedit revised an earlier changeset. Replaying a later edit to the next line stopped at a conflict and, once resolved, kept both changes; a later edit in a separate file replayed cleanly. hg backout reversed a deliberate bad commit, and a separate Mercurial clone received the expected file. Conversion to Git was not part of that check. Earlier check record, October 1, 2026
Used Mercurial? Share your experience to help other readers choose.
Which product are we missing?
Know a product that belongs in this article? Tell us what it does differently and why it deserves a closer look. Newcomers welcome.
Readers and product teams can suggest candidates. Suggestions inform our research; they do not guarantee inclusion or a recommendation.
Opens an email draft with this article attached as a link. Nothing is sent until you send it.
No email app? Send the product name, website, and this article’s title to admin@practicalpicks.guide.
What people are saying
We have no Practical Picks reader reviews for these tools yet.
Jujutsu draws the most discussion. LWN.net’s 2024 review found it usable for simple everyday work but missing several Git features, and said it was unclear whether it would be adopted outside Google. The most persistent request from its users is Git hook support: a discussion opened in June 2022 was still drawing requests in September 2026 for pre-commit, pre-push and commit-message checks. A maintainer replied there that “There’s no support for git hooks yet” and pointed to other built-in ways of running tools. Hooks discussion, LWN.net review
Homebrew’s install counts for the 12 months to October 19, 2026 give a rough sense of use among the macOS and Linux developers who use it: about 1.45 million installs for Git, 45,000 for Jujutsu and 17,600 for Mercurial. They are not market shares. Git, Jujutsu, Mercurial
How we researched
This is public-source research. For this review we did not install, run or test any of these tools, create accounts or contact the projects. Our sources were each project’s documentation, release notes, security advisories (GitHub, NVD, OSV and CISA), issue trackers and governance files, package records (Homebrew, Debian and PyPI), independent reporting (LWN.net and DevClass) and user discussions, read on October 19, 2026, with releases, security advisories, prices and newer tools rechecked on November 12, 2026. No project supplied access or payment, and our links carry no affiliate tracking.
This article first appeared on October 1, 2026, and then rested mainly on a small hands-on check run that day, before we adopted our research-only method on October 3. We keep that check as a dated observation. On Linux, the three tools edited an earlier commit in a three-line text file while keeping a later edit, recovered a deliberate mistake and handed the result to a separate local copy. It shows that those steps worked once in that setup, not how the tools behave at scale, with remote collaborators or against hostile repositories, and it did not decide any recommendation here. Earlier check record, October 1, 2026
We wrote this for a solo developer who keeps a small code project on their own computer, revises its history before sharing it, sometimes needs to undo a mistake, and then hands the repository to another developer. Before scoring, we fixed four criteria and their weights: history editing and recovery (30%), handoff and compatibility (30%), maintenance, security and continuity (25%), and setup, documentation and support (15%). Cost carried no weight: Git, Jujutsu, Mercurial and GitButler are free, and we could not confirm Sapling’s price, so the November price recheck changed no score. Git led by three-quarters of a point on our five-point scale and stayed ahead, narrowly, when we gave history editing half the weight. Jujutsu came first only when history editing carried about 60% and handoff 10%, which is why we name it for developers who rewrite their own history often. Mercurial came first only when we scored the handoff for a recipient who already uses Mercurial, which is why we name it for that case.
We checked that every widely used option for this reader was either compared or set aside for a stated reason. Sapling and GitButler passed our fit test and are compared above. The rest:
- Fossil deliberately has no rebase or other history rewriting.
- Subversion keeps history on a central server.
- Pijul and Darcs use their own repository formats and state no way to hand a project to someone using Git or Mercurial. Darcs’ latest release listed on its home page is from January 2025.
- Breezy says on its home page that Windows is not yet supported.
- Game of Trees lists Linux, the BSDs and macOS as supported systems, not Windows.
- git-branchless adds undo to Git rather than replacing it.
- Xit, a Git-compatible tool posted in April 2026 but with a dated commit from October 2024, falls outside the newer-entrant window, has no tagged release yet, builds from source, does not yet have a
pullcommand and lists no rebase or revert. - Haxy is a Git forge, and Epic Games’ Lore, released in June 2026, is a centralised system for large game assets. Other new tools we found are server-based systems for very large repositories used mostly by AI agents, or were early demonstrations.
Interfaces built on top of Jujutsu are not separate tools.
On November 12, 2026 we searched Hacker News, GitHub topic pages and the projects’ own pages again for newer tools. We name no Rising Star. Jujutsu, which we had earlier named a newcomer to consider, first shipped in March 2022, so it is no longer inside the two-year window for newer entrants, and no tool we found is both newer than November 2024 and ready to do this job. GitButler’s client opened in February 2024 and Sapling’s in 2022. That is a search result, not proof that no such tool exists.
| Tool | Public sources | What remains uncertain |
|---|---|---|
| Git | Project site and licence, rebase, revert, reflog and git history documentation, 2.54 to 2.56.1 release notes, planned breaking changes, Git and Git for Windows advisories, NVD and CISA records, Ubuntu security notice. | Fix status of one September 2026 Git for Windows advisory, the lack of a patched version on the November Git advisory page, Git 3.0 timing, whether the October 1 system’s package carried the backported fix. |
| Jujutsu | README, governance, operation-log, Git-compatibility and installation documentation, releases 0.3.0 to 0.47.1, three advisories, issue tracker, hooks discussion, LWN.net review, ERSC announcement, Homebrew and Debian records. | Google’s future role, the start-up’s effect on priorities, how often conflicts or repository damage occur in practice, reliability in larger projects. |
| Sapling | Git support modes, installation and getting-started pages, releases page, Hacker News post on its 2022 release. | Price and licence, amend and undo documentation, security record, whether the Git caveats affect a small handoff. |
| GitButler | CLI overview and installation pages, home page, repository and release notes 0.23.3 and 0.23.4, Hacker News posts on its 2024 opening. | Security record, how often the workspace branch affects a handoff, how long the Git LFS warning applies. |
| Mercurial | About and downloads pages, histedit, backout and clone help, PyPI release history, OSV records, hg-git package page, DevClass report. | hg-git compatibility with Mercurial 7.2, long-term hosting options. |
None of these sources measures speed, failure rates or behaviour with remote collaborators. Next substantive review is due December 18, 2026, or sooner if a security advisory or a Jujutsu release changes this job. Found a change? Contact the editors.
Sources and evidence
Checked October 19 and November 12, 2026: Git project and licence, downloads and current release, 2.56.0 release notes, planned breaking changes, rebase, revert, reflog, git history, security advisories, November 2026 advisory, CVE-2025-48384 advisory, CISA exploited-vulnerabilities catalog, Git for Windows advisories and Ubuntu USN-7626-1; Jujutsu project README, governance, 0.46.0 release, 0.3.0 release, operation log, Git compatibility, installation, advisories GHSA-88h5-6w7m-5w56, GHSA-gg38-mhjq-j4mp and GHSA-794x-2rpg-rfgr, issues 9649 and 8511, hooks discussion, LWN.net review and ERSC announcement; Mercurial project and licence, downloads, 7.2.4 release; histedit, backout, clone and hg-git; Sapling Git support modes, installation and getting started (read November 12, 2026); GitButler CLI overview, project and releases (read November 12, 2026); Opening Up GitButler; DevClass on Mozilla’s move to Git; Homebrew records for Git, Jujutsu and Mercurial; and the earlier check record, October 1, 2026. No project supplied access or influenced the conclusion. No affiliate links were used. Recheck versions, advisories and Jujutsu’s compatibility page before any public release.
No screenshots are shown: these are command-line tools, and this review is based on public sources. The earlier check record, October 1, 2026 describes the synthetic text file used in a small check before our research-only method.