1. 04 12月, 2008 1 次提交
  2. 08 11月, 2007 1 次提交
  3. 06 11月, 2007 1 次提交
  4. 03 7月, 2007 1 次提交
  5. 06 4月, 2007 1 次提交
    • S
      Fix lost-found to show commits only referenced by reflogs · 566842f6
      Shawn O. Pearce 提交于
      Prior to 1.5.0 the git-lost-found utility was useful to locate
      commits that were not referenced by any ref.  These were often
      amends, or resets, or tips of branches that had been deleted.
      Being able to locate a 'lost' commit and recover it by creating a
      new branch was a useful feature in those days.
      
      Unfortunately 1.5.0 added the reflogs to the reachability analysis
      performed by git-fsck, which means that most commits users would
      consider to be lost are still reachable through a reflog.  So most
      (or all!) commits are reachable, and nothing gets output from
      git-lost-found.
      
      Now git-fsck can be told to ignore reflogs during its reachability
      analysis, making git-lost-found useful again to locate commits
      that are no longer referenced by a ref itself, but may still be
      referenced by a reflog.
      Signed-off-by: NShawn O. Pearce <spearce@spearce.org>
      Signed-off-by: NJunio C Hamano <junkio@cox.net>
      566842f6
  6. 29 1月, 2007 1 次提交
  7. 28 7月, 2006 1 次提交
  8. 14 12月, 2005 1 次提交
  9. 29 11月, 2005 1 次提交
  10. 26 11月, 2005 1 次提交
  11. 13 11月, 2005 1 次提交
  12. 12 11月, 2005 2 次提交