1. 20 9月, 2008 6 次提交
  2. 19 9月, 2008 15 次提交
  3. 16 9月, 2008 4 次提交
  4. 13 9月, 2008 3 次提交
  5. 12 9月, 2008 1 次提交
  6. 11 9月, 2008 6 次提交
  7. 10 9月, 2008 5 次提交
    • J
      Merge branch 'jc/maint-log-grep' into maint · a14f6ca2
      Junio C Hamano 提交于
      * jc/maint-log-grep:
        log --author/--committer: really match only with name part
      a14f6ca2
    • J
      Merge branch 'jc/maint-hide-cr-in-diff-from-less' into maint · 26c10c7a
      Junio C Hamano 提交于
      * jc/maint-hide-cr-in-diff-from-less:
        diff: Help "less" hide ^M from the output
      26c10c7a
    • J
      Merge branch 'jc/maint-checkout-fix' into maint · 94c27881
      Junio C Hamano 提交于
      * jc/maint-checkout-fix:
        checkout: do not check out unmerged higher stages randomly
      94c27881
    • J
      Merge branch 'np/maint-safer-pack' into maint · 9f35e5fd
      Junio C Hamano 提交于
      * np/maint-safer-pack:
        fixup_pack_header_footer(): use nicely aligned buffer sizes
        index-pack: use fixup_pack_header_footer()'s validation mode
        pack-objects: use fixup_pack_header_footer()'s validation mode
        improve reliability of fixup_pack_header_footer()
        pack-objects: improve returned information from write_one()
      9f35e5fd
    • J
      checkout: do not lose staged removal · 55218834
      Junio C Hamano 提交于
      The logic to checkout a different commit implements the safety to never
      lose user's local changes.  For example, switching from a commit to
      another commit, when you have changed a path that is different between
      them, need to merge your changes to the version from the switched-to
      commit, which you may not necessarily be able to resolve easily.  By
      default, "git checkout" refused to switch branches, to give you a chance
      to stash your local changes (or use "-m" to merge, accepting the risks of
      getting conflicts).
      
      This safety, however, had one deliberate hole since early June 2005.  When
      your local change was to remove a path (and optionally to stage that
      removal), the command checked out the path from the switched-to commit
      nevertheless.
      
      This was to allow an initial checkout to happen smoothly (e.g. an initial
      checkout is done by starting with an empty index and switching from the
      commit at the HEAD to the same commit).  We can tighten the rule slightly
      to allow this special case to pass, without losing sight of removal
      explicitly done by the user, by noticing if the index is truly empty when
      the operation begins.
      
      For historical background, see:
      
          http://thread.gmane.org/gmane.comp.version-control.git/4641/focus=4646
      
      This case is marked as *0* in the message, which both Linus and I said "it
      feels somewhat wrong but otherwise we cannot start from an empty index".
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      55218834