martinvonz/jj
1
1
Fork 0
mirror of https://github.com/martinvonz/jj.git synced 2024-08-15 16:50:30 +03:00
Code Issues Packages Projects Releases Wiki Activity

docs: add a "Related Work" section to README

Browse Source
This commit is contained in:
Martin von Zweigbergk 2021-10-20 15:27:33 -07:00 committed by Martin von Zweigbergk
parent 60ea81882f
commit 5c0e929b29
2 changed files with 23 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -125,3 +125,9 @@ email = "martinvonz@google.com"
The best way to get started is probably to go through
[the tutorial](docs/tutorial.md).
## Related work
There are several tools trying to solve similar problems as Jujutsu. See
[related work](docs/related_work.md) for details.

17
docs/related_work.md Normal file
View File

@ -0,0 +1,17 @@
# Related work
Similar tools:
* [git-branchless](https://github.com/arxanas/git-branchless): Helps you use a
branchless workflow in your Git repo. Supports anonymous branching, undo,
and faster rebase (`git move`). Under heavy development and quickly gaining
new features.
* [GitUp](https://gitup.co/): A Mac-only GUI for Git. Like Jujutsu, supports
undo and restoring the repo to an earlier snapshot. Backed by its
[GitUpKit library](https://github.com/git-up/GitUp#gitupkit).
* [Gitless](https://gitless.com/): Another attempt at providing a simpler
interface for Git. Like Jujutsu, does not have an "index"/"staging area"
concept. Also doesn't move the working copy changes between branches (which
we do simply as a consequence of making the working copy a commit).
* [Pijul](https://pijul.org/): Architecturally quite different from Jujutsu,
but its "first-class conflicts" feature seems quite similar to ours.