1. 19 4月, 2010 1 次提交
  2. 18 4月, 2010 2 次提交
    • M
      t1010-mktree: Adjust expected result to code and documentation · 53b3c47d
      Michael J Gruber 提交于
      The last two tests here were always supposed to fail in the sense
      that, according to code and documentation, mktree should read non-recursive
      ls-tree output, but not recursive one, and therefore explicitely refuses
      to deal with slashes.
      
      Adjust the test (must_fail) so that it succeeds when mktree dies on
      slashes.
      Signed-off-by: NMichael J Gruber <git@drmicha.warpmail.net>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      53b3c47d
    • T
      combined diff: correctly handle truncated file · 21798708
      Thomas Rast 提交于
      Consider an evil merge of two commits A and B, both of which have a
      file 'foo', but the merge result does not have that file.
      
      The combined-diff code learned in 4462731e (combine-diff: do not punt
      on removed or added files., 2006-02-06) to concisely show only the
      removal, since that is the evil part and the previous contents are
      presumably uninteresting.
      
      However, to diagnose an empty merge result, it overloaded the variable
      that holds the file's length.  This means that the check also triggers
      for truncated files.  Consequently, such files were not shown in the
      diff at all despite the merge being clearly evil.
      
      Fix this by adding a new variable that distinguishes whether the file
      was deleted (which is the case 4462731e handled) or truncated.  In the
      truncated case, we show the full combined diff again, which is rather
      spammy but at least does not hide the evilness.
      Reported-by: NDavid Martínez Martí <desarrollo@gestiweb.com>
      Signed-off-by: NThomas Rast <trast@student.ethz.ch>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      21798708
  3. 15 4月, 2010 1 次提交
    • J
      Document new "already-merged" rule for branch -d · fff0d0ab
      Jonathan Nieder 提交于
      v1.7.0-rc0~18^2 (branch -d: base the "already-merged" safety on the
      branch it merges with, 2009-12-29) taught ‘git branch’ a new heuristic
      for when it is safe to delete a branch without forcing the issue.  It
      is safe to delete a branch "topic" without second thought if:
      
       - the branch "topic" is set up to pull from a (remote-tracking,
         usually) branch and is fully merged in that "upstream" branch, or
      
       - there is no branch.topic.merge configuration and branch "topic" is
         fully merged in the current HEAD.
      
      Update the man page to acknowledge the new rules.
      Signed-off-by: NJonathan Nieder <jrnieder@gmail.com>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      fff0d0ab
  4. 14 4月, 2010 1 次提交
  5. 13 4月, 2010 1 次提交
  6. 12 4月, 2010 3 次提交
  7. 10 4月, 2010 12 次提交
  8. 09 4月, 2010 1 次提交
  9. 05 4月, 2010 2 次提交
  10. 01 4月, 2010 6 次提交
  11. 31 3月, 2010 4 次提交
  12. 30 3月, 2010 1 次提交
  13. 29 3月, 2010 5 次提交