It still says Switched to a new branch, but first it says Branch 'maint' set up to track remote branch 'maint' from 'origin'. On the other hand, I don't have a branch named maint, and yet: $ git checkout maintīranch 'maint' set up to track remote branch 'maint' from 'origin'.
Git tried to treat asdfasdf as a file name, and I don't have a file named asdfasdf either. This failed because I don't have a branch asdfasdf. So for most repositories you shouldn't need to explicitly run git gc all that often, since it will already be taken care of for you.Įrror: pathspec 'asdfasdf' did not match any file(s) known to git Some gitĬommands run git gc -auto after performing operations that could With this option, git gc checks whether any housekeeping is required if not, it exits without performing any work. However, keep in mind that a garbage collection may already be triggered automatically following certain commands, unless this behavior is disabled by the setting the gc.auto configuration variable to 0. In general it's better to run git gc -auto simply because it will do the least amount of work necessary to keep the repository in good shape – safely and without wasting too many resources. Which one is better to use in regard to space optimization or safety? keep file) areĬonsolidated into a single pack by using the -A option of git repack.Īs you can see, git gc strives to do the right thing based on the state of the repository. If the number of packs exceeds the value of gc.autoPackLimit, thenĮxisting packs (except those marked with a.
Setting the value of gc.auto to 0 disables automatic packing of Objects are combined into a single pack using git repack -d -l. The value of the gc.auto configuration variable, then all loose Housekeeping is required if there are too many loose objects or too This is further clarified in the documentation: Notice on line 211-212 of the need_for_gc function that if there aren't enough loose objects in the repository, gc is not run at all.
#Git repack code
More specifically, by looking at the source code of gc.c (lines 338-343) 1 we can see that it invokes at the most the following commands:ĭepending on the number of packs (lines 121-126), it may run repack with -A option instead (lines 203-212): * If there are too many loose objects, but not too many If yes, what additional steps will be done by git gc (or vice versa)?Īccording to the documentation, git gc runs: Also, git gc is going to run more tasks than just git repack and git prune.
For example, it won't run git repack unless the number of loose objects in the repository is above a certain threshold (configurable via the gc.auto variable). The difference is that by default git gc is very conservative about what housekeeping tasks are needed. Is there any difference between git gc and git repack -ad git prune?
0 kommentar(er)
