1. 04 5月, 2006 3 次提交
  2. 03 5月, 2006 2 次提交
  3. 30 4月, 2006 1 次提交
  4. 29 4月, 2006 6 次提交
  5. 28 4月, 2006 2 次提交
  6. 27 4月, 2006 3 次提交
  7. 25 4月, 2006 4 次提交
  8. 22 4月, 2006 1 次提交
  9. 21 4月, 2006 4 次提交
  10. 20 4月, 2006 3 次提交
    • J
      git-commit --amend: two fixes. · 6a74642c
      Junio C Hamano 提交于
      When running "git commit --amend" only to fix the commit log
      message without any content change, we mistakenly showed the
      git-status output that says "nothing to commit" without
      commenting it out.
      
      If you have already run update-index but you want to amend the
      top commit, "git commit --amend --only" without any paths should
      have worked, because --only means "starting from the base
      commit, update-index these paths only to prepare the index to
      commit, and perform the commit".  However, we refused -o without
      paths.
      Signed-off-by: NJunio C Hamano <junkio@cox.net>
      6a74642c
    • J
      pre-commit hook: complain about conflict markers. · 61c2bcbd
      Junio C Hamano 提交于
      Several <<< or === or >>> characters at the beginning of a line
      is very likely to be leftover conflict markers from a failed
      automerge the user resolved incorrectly, so detect them.
      
      As usual, this can be defeated with "git commit --no-verify" if
      you really do want to have those files, just like changes that
      introduce trailing whitespaces.
      Signed-off-by: NJunio C Hamano <junkio@cox.net>
      61c2bcbd
    • J
      git-merge: a bit more readable user guidance. · 50ac7408
      Junio C Hamano 提交于
      We said "fix up by hand" after failed automerge, which was a big
      "Huh?  Now what?".  Be a bit more explicit without being too
      verbose. Suggested by Carl Worth.
      Signed-off-by: NJunio C Hamano <junkio@cox.net>
      50ac7408
  11. 19 4月, 2006 5 次提交
  12. 18 4月, 2006 6 次提交