1. 07 Sep, 2010 1 commit
  2. 22 Aug, 2010 1 commit
  3. 23 Dec, 2009 1 commit
  4. 21 Dec, 2009 1 commit
  5. 20 Dec, 2009 1 commit
  6. 16 Dec, 2009 1 commit
  7. 11 Dec, 2009 1 commit
  8. 10 Dec, 2009 1 commit
  9. 09 Dec, 2009 1 commit
  10. 02 Dec, 2009 1 commit
  11. 01 Dec, 2009 1 commit
  12. 28 Nov, 2009 1 commit
  13. 23 Nov, 2009 1 commit
  14. 16 Nov, 2009 1 commit
  15. 26 Oct, 2009 1 commit
  16. 20 Oct, 2009 1 commit
    • Junio C Hamano's avatar
      fsck: default to "git fsck --full" · f29cd393
      Junio C Hamano authored
      Linus and other git developers from the early days trained their fingers
      to type the command, every once in a while even without thinking, to check
      the consistency of the repository back when the lower core part of the git
      was still being developed.  Developers who wanted to make sure that git
      correctly dealt with packfiles could deliberately trigger their creation
      and checked them after they were created carefully, but loose objects are
      the ones that are written by various commands from random codepaths.  It
      made some technical sense to have a mode that checked only loose objects
      from the debugging point of view for that reason.
      
      Even for git developers, there no longer is any reason to type "git fsck"
      every five minutes these days, worried that some newly created objects
      might be corrupt due to recent change to git.
      
      The reason we did not make "--full" the default is probably we trust our
      filesystems a bit too much.  At least, we trusted filesystems more than we
      trusted the lower core part of git that was under development.
      
      Once a packfile is created and we always use it read-only, there didn't
      seem to be much point in suspecting that the underlying filesystems or
      disks may corrupt them in such a way that is not caught by the SHA-1
      checksum over the entire packfile and per object checksum.  That trust in
      the filesystems might have been a good tradeoff between fsck performance
      and reliability on platforms git was initially developed on and for, but
      it may not be true anymore as we run on many more platforms these days.
      Signed-off-by: default avatarJunio C Hamano <[email protected]>
      f29cd393
  17. 17 Oct, 2009 1 commit