git_fsck

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
git_fsck [2019/03/06 08:38] – [SYNOPSIS] rpjdaygit_fsck [2019/03/12 15:21] (current) – [Overview] rpjday
Line 1: Line 1:
 ===== Overview ===== ===== Overview =====
  
-Using ''git fsck'' to display dangling and unreachable objects.+Using ''git fsck'' to display dangling and unreachable objects (should cover reflog first). 
 + 
 +Check: 
 + 
 +  * Does ''%%--%%lost-found'' save blobs? Don't think so.
  
 ===== SYNOPSIS ===== ===== SYNOPSIS =====
Line 18: Line 22:
  
 <code> <code>
-                A<-----B<-----C+                A<-----B<-----C   [no reference to this]
                /                /
               /               /
Line 24: Line 28:
 </code> </code>
  
-If nothing points at C, then all of A, B and C are unreachable, but only C is dangling.+  * unreachable: A, B, and C 
 +  * dangling: C only
  
 ===== OPTIONS ===== ===== OPTIONS =====
Line 48: Line 53:
 </code> </code>
  
-''%%--%%unreachable'' overrides ''%%--%%no-dangling''.+Note that ''%%--%%unreachable'' overrides ''%%--%%no-dangling''.
  
 ===== Examples ===== ===== Examples =====
Line 161: Line 166:
 dangling commit 99fd08769f3e7c134c4fc97c76edd5e9b4c9e562 dangling commit 99fd08769f3e7c134c4fc97c76edd5e9b4c9e562
 $ $
 +</code>
 +
 +===== Config options =====
 +
 +<code>
 +fsck.skipList
 +    The path to a list of object names (i.e. one unabbreviated
 +    SHA-1 per line) that are known to be broken in a non-fatal
 +    way and should be ignored. On versions of Git 2.20 and
 +    later comments (#), empty lines, and any leading and
 +    trailing whitespace is ignored. Everything but a SHA-1 per
 +    line will error out on older versions.
 </code> </code>
  • git_fsck.1551861500.txt.gz
  • Last modified: 2019/03/06 08:38
  • by rpjday