ok/jj
1
0
Fork 0
forked from mirrors/jj
Code Pull requests Activity

docs: mention git pack-refs for co-located repos

Browse source 
As suggested by @yuja in
https://github.com/martinvonz/jj/issues/1841#issuecomment-1720451152

Thanks to @lazywei for pointing out that `git pack-refs --all` is better, at
least on the first run. I haven't checked, but suspect, that because of the
number of `refs/jj` refs jj creates, it might always be better.
This commit is contained in:
Ilya Grigoriev 2023-09-14 21:23:12 -07:00
parent f31e66d663
commit c5f74bc466
1 changed files with 5 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
docs/git-compatibility.md
View file

@ -128,6 +128,11 @@ repos may require you to deal with more involved Jujutsu and Git concepts.
it because they automatically run `git fetch` in the background from time to it because they automatically run `git fetch` in the background from time to
time. time.
* In co-located repos with a very large number of branches or other refs, `jj`
commands can get noticeably slower because of the automatic `jj git import`
executed on each command. This can be mitigated by occasionally running `git
pack-refs --all` to speed up the import.
* Git tools will have trouble with revisions that contain conflicted files. While * Git tools will have trouble with revisions that contain conflicted files. While
`jj` renders these files with conflict markers in the working copy, they are `jj` renders these files with conflict markers in the working copy, they are
stored in a non-human-readable fashion inside the repo. Git tools will often stored in a non-human-readable fashion inside the repo. Git tools will often