Original: http://gitbook.liuhui998.com/4_10.html
first, to ensure that git good performanceIn large warehouses, git compresses historical information to conserve disk and memory space. Compression is not automatic, you need to manually perform git gc:$ git gc compression is time consuming, it is best to run the git GC command when you have no other job.
second, to maintain the reliability of GitGit fsck runs a consistency check on some warehouses and reports if there are any problems. This is also a time-consuming operation, and the usual warning is "dangling objects" (dangling objects). $ git fsckdangling Commit 7281251ddd2a61e38657c827739c57015671a6b3dangling Commit 2706a059f258c6b245f298dc4ff2ccd30ec21a63dangling Commit 13472b7c4b80851a1bc551779171dcb03655e9b5dangling BLOB 218761f9d90712d37a9c5e36f406f92202db07ebdangling Commit Bf093535a34a4d35731aa2bd90fe6b176302f14fdangling Commit 8e4bec7f2ddaa268bef999853c25755452100f8edangling Tree D50bb86186bf27b681d25af89d3b5b68382e4085dangling tree b24c2473f1fd3d91352a624795be026d64c8841f ... "dangling objects" (dangling objects) is not a problem, but the worst case scenario is that they take up more disk space. Sometimes they are the last glimmer of hope to get the lost job back.
-
Top
-
0
-
Step
-
0
git maintenance (git gc and git fsck)
