Skip to content

Commit

Permalink
docs: mention git pack-refs for co-located repos
Browse files Browse the repository at this point in the history
As suggested by @yuja in
jj-vcs#1841 (comment)

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.
  • Loading branch information
ilyagr committed Sep 16, 2023
1 parent 2177dc0 commit c11e90c
Showing 1 changed file with 5 additions and 0 deletions.
5 changes: 5 additions & 0 deletions docs/git-compatibility.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
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
`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
Expand Down

0 comments on commit c11e90c

Please sign in to comment.