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: explain that the there's no reason to use the native backend

Browse Source 
A few people in different forums asked if there's any reason to use
the native backend and what the reason for its existance is, so let's
document that.
This commit is contained in:
Martin von Zweigbergk 2022-03-05 08:42:35 -08:00 committed by Martin von Zweigbergk
parent 32e22831fc
commit 630f8069d0
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -32,10 +32,14 @@ to replace (rare in English). The project is called "Jujutsu" because it matches
### Compatible with Git
Jujutsu has two backends. One of them is a Git backend (the other is a native
one). This lets you use Jujutsu as an alternative interface to Git. The commits
one [^native-backend]). This lets you use Jujutsu as an alternative interface to Git. The commits
you create will look like regular Git commits. You can always switch back to
Git. The Git support uses the [libgit2](https://libgit2.org/) C library.
[^native-backend]: There's currently practically no reason to use the native
backend. It exists to make sure that it's possible to eventually add
functionality that cannot easily be added the Git backend.
<a href="https://asciinema.org/a/DRCzktCyEAxH6j788ZDT6aSjS" target="_blank">
<img src="https://asciinema.org/a/DRCzktCyEAxH6j788ZDT6aSjS.svg" />
</a>