![]() Linus suggested (see below for the full mailing list post) using git gc -aggressive only when you have, in his words, “a really bad pack” or “really horribly bad deltas,” however “almost always, in other cases, it’s actually a really bad thing to do.” The result may even leave your repository in worse condition than when you started! A window of size 250 is good because it scans a larger section of each object, but depth at 250 is bad because it makes every chain refer to very deep old objects, which slows down all future git operations for marginally lower disk usage. As of version 2.11 (Q4 2016), git defaults to a depth of 50. Nowadays there is no difference: git gc -aggressive operates according to the suggestion Linus made in 2007 see below.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |