1. 12 9月, 2012 24 次提交
  2. 11 9月, 2012 11 次提交
    • J
      Start preparing for 1.7.12.1 · 23193cfd
      Junio C Hamano 提交于
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      23193cfd
    • J
      Merge branch 'bc/prune-info' into maint · f56d036c
      Junio C Hamano 提交于
      "git prune" without "-v" used to warn about leftover temporary
      files (which is an indication of an earlier aborted operation).
      
      * bc/prune-info:
        prune.c: only print informational message in show_only or verbose mode
      f56d036c
    • J
      Merge branch 'maint-1.7.11' into maint · e3f26752
      Junio C Hamano 提交于
      * maint-1.7.11:
        Almost 1.7.11.6
        gitweb: URL-decode $my_url/$my_uri when stripping PATH_INFO
        rebase -i: use full onto sha1 in reflog
        sh-setup: protect from exported IFS
        receive-pack: do not leak output from auto-gc to standard output
        t/t5400: demonstrate breakage caused by informational message from prune
        setup: clarify error messages for file/revisions ambiguity
        send-email: improve RFC2047 quote parsing
        fsck: detect null sha1 in tree entries
        do not write null sha1s to on-disk index
        diff: do not use null sha1 as a sentinel value
      e3f26752
    • J
      Almost 1.7.11.6 · 9a8eea96
      Junio C Hamano 提交于
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      9a8eea96
    • J
      Merge branch 'mg/rebase-i-onto-reflog-in-full' into maint-1.7.11 · 73eb89e7
      Junio C Hamano 提交于
      The reflog entries left by "git rebase" and "git rebase -i" were
      inconsistent (the interactive one gave an abbreviated object name).
      
      * mg/rebase-i-onto-reflog-in-full:
        rebase -i: use full onto sha1 in reflog
      73eb89e7
    • J
      Merge branch 'jc/maint-protect-sh-from-ifs' into maint-1.7.11 · 7cc51cfe
      Junio C Hamano 提交于
      When the user exports a non-default IFS without HT, scripts that
      rely on being able to parse "ls-files -s | while read a b c..."
      start to fail.  Protect them from such a misconfiguration.
      
      * jc/maint-protect-sh-from-ifs:
        sh-setup: protect from exported IFS
      7cc51cfe
    • J
      Merge branch 'bc/receive-pack-stdout-protection' into maint-1.7.11 · 3f664638
      Junio C Hamano 提交于
      When "git push" triggered the automatic gc on the receiving end, a
      message from "git prune" that said it was removing cruft leaked to
      the standard output, breaking the communication protocol.
      
      * bc/receive-pack-stdout-protection:
        receive-pack: do not leak output from auto-gc to standard output
        t/t5400: demonstrate breakage caused by informational message from prune
      3f664638
    • J
      Merge branch 'jk/maint-null-in-trees' into maint-1.7.11 · 03adeeaa
      Junio C Hamano 提交于
      "git diff" had a confusion between taking data from a path in the
      working tree and taking data from an object that happens to have
      name 0{40} recorded in a tree.
      
      * jk/maint-null-in-trees:
        fsck: detect null sha1 in tree entries
        do not write null sha1s to on-disk index
        diff: do not use null sha1 as a sentinel value
      03adeeaa
    • J
      Merge branch 'tr/maint-send-email-2047' into maint-1.7.11 · 423a9e28
      Junio C Hamano 提交于
      "git send-email" did not unquote encoded words that appear on the
      header correctly, and lost "_" from strings.
      
      * tr/maint-send-email-2047:
        send-email: improve RFC2047 quote parsing
      423a9e28
    • J
      Merge branch 'mm/die-with-dashdash-help' into maint-1.7.11 · 5f9d8e35
      Junio C Hamano 提交于
      When the user gives an argument that can be taken as both a
      revision name and a pathname without disambiguating with "--", we
      used to give a help message "Use '--' to separate".  The message
      has been clarified to show where that '--' goes on the command
      line.
      
      * mm/die-with-dashdash-help:
        setup: clarify error messages for file/revisions ambiguity
      5f9d8e35
    • J
      Merge branch 'js/gitweb-path-info-unquote' into maint-1.7.11 · 3d4003bd
      Junio C Hamano 提交于
      "gitweb" when used with PATH_INFO failed to notice directories with
      SP (and other characters that need URL-style quoting) in them.
      
      * js/gitweb-path-info-unquote:
        gitweb: URL-decode $my_url/$my_uri when stripping PATH_INFO
      3d4003bd
  3. 25 8月, 2012 5 次提交
    • J
      Merge branch 'maint-1.7.11' into maint · 871e293c
      Junio C Hamano 提交于
      * maint-1.7.11:
        Prepare for 1.7.11.6
        Make the ciabot scripts completely self-configuring in the normal case.
        Improved documentation for the ciabot scripts.
        man: git pull -r is a short for --rebase
        gitcli: describe abbreviation of long options
        rev-list docs: clarify --topo-order description
        Documentation/CodingGuidelines: spell out more shell guidelines
        Documentation: do not mention .git/refs/* directories
        tests: Introduce test_seq
      871e293c
    • J
      Prepare for 1.7.11.6 · b5218317
      Junio C Hamano 提交于
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      b5218317
    • J
      Merge branch 'mv/pull-r-for-rebase' into maint-1.7.11 · 1103996e
      Junio C Hamano 提交于
      A minor documentation update.
      
      * mv/pull-r-for-rebase:
        man: git pull -r is a short for --rebase
      1103996e
    • J
      Merge branch 'jc/maint-abbrev-option-cli' into maint-1.7.11 · bdb30339
      Junio C Hamano 提交于
      We did not document that many commands take unique prefix
      abbreviations of long options (e.g. "--option" may be the only flag
      that the command accepts that begin with "--opt", in which case you
      can give "--opt") anywhere easy to find for new people.
      
      * jc/maint-abbrev-option-cli:
        gitcli: describe abbreviation of long options
      bdb30339
    • J
      Merge branch 'jc/maint-rev-list-topo-doc' into maint-1.7.11 · 7939a334
      Junio C Hamano 提交于
      It was unclear what "--topo-order" was really about in the
      documentation. It is not just about "children before parent", but
      also about "don't mix lineages".
      
      * jc/maint-rev-list-topo-doc:
        rev-list docs: clarify --topo-order description
      7939a334