-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add pack-refs steps #382
Comments
For me it speeds up |
Labeling this issue as stale. There has been no activity for 30 days. Remove stale label or comment or this issue will be closed in 7 days. |
Labeling this issue as stale. There has been no activity for 30 days. Remove stale label or comment or this issue will be closed in 7 days. |
@sluongng @shalupov: Thank you for creating and commenting here. I'm finally getting around to putting this into core Git instead of Scalar. See gitgitgadget/git#871 for more details. Thanks! |
Labeling this issue as stale. There has been no activity for 30 days. Remove stale label or comment or this issue will be closed in 7 days. |
Hah. This is in Git 2.31.1, so is enabled by default when using Git's background maintenance. Closing. |
Problem
For a large repository, and given some particular workflow, there are many refs(branches / tags) that user will have to deal with.
Too many unpacked-refs will lead to slowness in
git for-each-ref
, which is often used in developers' shell completions script. This, in turn, led to a sluggish User Experience when user want to checkout a branch/tag.Proposal
Implement pack-refs steps in the background where
git pack-refs --all
is called routinely. This would help clean up loose refs, save the inodes and speed upfor-each-ref
call overall.The text was updated successfully, but these errors were encountered: