1. 10 11月, 2009 4 次提交
    • J
      Show usage string for 'git commit-tree -h' · 6e9daeff
      Jonathan Nieder 提交于
      Treat an "-h" option as a request for help, rather than a "Not a
      valid object name" error.
      
      "commit-tree -h" could be asking to create a new commit from a
      treeish named "-h".  Strictly speaking, such a pathological ref
      name is possible, but the user would have to had said something
      like "tags/-h" to name such a pathological already.  commit-tree
      is usually used in scripts with raw object ids, anyway.
      
      For consistency, the "-h" option uses its new meaning even if
      followed by other arguments.
      Signed-off-by: NJonathan Nieder <jrnieder@gmail.com>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      6e9daeff
    • J
      Show usage string for 'git cherry -h' · fef34270
      Jonathan Nieder 提交于
      Treat an "-h" option as a request for help, rather than an
      "Unknown commit -h" error.
      
      "cherry -h" could be asking to compare histories that leads to
      our HEAD and a commit that can be named as "-h".  Strictly
      speaking, that may be a valid refname, but the user would have to
      say something like "tags/-h" to name such a pathological ref
      already, so it is not such a big deal.
      
      The "-h" option keeps its meaning even if preceded by other
      options or followed by other arguments.  This keeps the
      command-line syntax closer to what parse_options would give and
      supports shell aliases like 'alias cherry="git cherry -v"' a
      little better.
      Signed-off-by: NJonathan Nieder <jrnieder@gmail.com>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      fef34270
    • J
      Show usage string for 'git grep -h' · 9c855c31
      Jonathan Nieder 提交于
      Clarification: the following description only talks about "git
      grep -h" without any other options and arguments.
      
      Such a change cannot be breaking backward compatibility.  "grep
      -h" cannot be asking for suppressing filenames, as there is no
      match pattern specified.
      Signed-off-by: NJonathan Nieder <jrnieder@gmail.com>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      9c855c31
    • J
      Retire fetch--tool helper to contrib/examples · fe9a2152
      Jonathan Nieder 提交于
      When git-fetch was builtin-ized, the previous script was moved to
      contrib/examples.  Now, it is the sole remaining user for
      'git fetch--tool'.
      
      The fetch--tool code is still worth keeping around so people can
      try out the old git-fetch.sh, for example when investigating
      regressions from the builtinifaction.
      Signed-off-by: NJonathan Nieder <jrnieder@gmail.com>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      fe9a2152
  2. 09 11月, 2009 2 次提交
  3. 07 11月, 2009 2 次提交
    • J
      Merge branch 'jc/commit-s-subject-is-not-a-footer' · 6e31f3db
      Junio C Hamano 提交于
      * jc/commit-s-subject-is-not-a-footer:
        builtin-commit.c: fix logic to omit empty line before existing footers
      6e31f3db
    • J
      builtin-commit.c: fix logic to omit empty line before existing footers · e5138436
      Junio C Hamano 提交于
      "commit -s" used to add an empty line before adding S-o-b line only when
      the last line of the existing log message is not another S-o-b line, but
      c1e01b0c (commit: More generous accepting of RFC-2822 footer lines.,
      2009-10-28) introduced logic to omit this empty line when the message ends
      with a run of "footer" lines, to cover S-o-b's friends, e.g. Acked-by.
      
      However, the logic was overzealous and missed one corner case.  A message
      that consists of a single line that begins with Token + colon, it can be
      mistaken as a S-o-b's friend.  We do want an empty line in such a case.
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      e5138436
  4. 06 11月, 2009 1 次提交
  5. 05 11月, 2009 2 次提交
  6. 04 11月, 2009 2 次提交
  7. 03 11月, 2009 2 次提交
  8. 02 11月, 2009 3 次提交
  9. 01 11月, 2009 1 次提交
  10. 31 10月, 2009 19 次提交
  11. 29 10月, 2009 2 次提交
    • J
      Merge branch 'maint' · cd0f8e6d
      Junio C Hamano 提交于
      * maint:
        help -a: do not unnecessarily look for a repository
        Do not try to remove directories when removing old links
        rebase -i: more graceful handling of invalid commands
        help -i: properly error out if no info viewer can be found
      cd0f8e6d
    • D
      commit: More generous accepting of RFC-2822 footer lines. · c1e01b0c
      David Brown 提交于
      'git commit -s' will insert a blank line before the Signed-off-by
      line at the end of the message, unless this last line is a
      Signed-off-by line itself.  Common use has other trailing lines
      at the ends of commit text, in the style of RFC2822 headers.
      
      Be more generous in considering lines to be part of this footer.
      If the last paragraph of the commit message reasonably resembles
      RFC-2822 formatted lines, don't insert that blank line.
      
      The new Signed-off-by line is still only suppressed when the
      author's existing Signed-off-by is the last line of the message.
      Signed-off-by: NDavid Brown <davidb@quicinc.com>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      c1e01b0c