1. 14 4月, 2009 1 次提交
  2. 08 4月, 2009 1 次提交
  3. 18 3月, 2009 1 次提交
  4. 03 3月, 2009 1 次提交
    • J
      send-email: add --confirm option and configuration setting · c1f2aa45
      Jay Soffian 提交于
      send-email violates the principle of least surprise by automatically
      cc'ing additional recipients without confirming this with the user.
      
      This patch teaches send-email a --confirm option. It takes the
      following values:
      
       --confirm=always   always confirm before sending
       --confirm=never    never confirm before sending
       --confirm=cc       confirm before sending when send-email has
                          automatically added addresses from the patch to
                          the Cc list
       --confirm=compose  confirm before sending the first message when
                          using --compose. (Needed to maintain backwards
                          compatibility with existing behavior.)
       --confirm=auto     'cc' + 'compose'
      
      If sendemail.confirm is unconfigured, the option defaults to 'compose'
      if any suppress-Cc related options have been used, otherwise it defaults
      to 'auto'.
      
      Unfortunately, it is impossible to introduce this patch such that it
      helps new users without potentially annoying some existing users. We
      attempt to mitigate the latter by:
      
       * Allowing the user to set 'git config sendemail.confirm never'
       * Allowing the user to say 'all' after the first prompt to not be
         prompted on remaining emails during the same invocation.
       * Telling the user about the 'sendemail.confirm' setting if it is
         unconfigured whenever we prompt due to Cc before sending.
       * Only prompting if no --suppress related options have been passed, as
         using such an option is likely to indicate an experienced send-email
         user.
      
      There is a slight fib in message informing the user of the
      sendemail.confirm setting and this is intentional. Setting 'auto'
      differs from leaving sendemail.confirm unset in two ways: 1) 'auto'
      obviously squelches the informational message; 2) 'auto' prompts when
      the Cc list has been expanded even in the presence of a --suppress
      related option, where leaving sendemail.confirm unset does not. This is
      intentional to keep the message simple, and to avoid adding another
      sendemail.confirm value ('auto-except-suppress'?).
      Signed-off-by: NJay Soffian <jaysoffian@gmail.com>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      c1f2aa45
  5. 19 2月, 2009 1 次提交
  6. 15 2月, 2009 1 次提交
    • J
      send-email: --suppress-cc improvements · 3531e270
      Jay Soffian 提交于
      Since 65648283 (git-send-email: Generalize auto-cc recipient
      mechanism., 2007-12-25) we can suppress automatic Cc generation
      separately for each of the possible address sources.  However,
      --suppress-cc=sob suppressed both SOB lines and body (but not header)
      Cc lines, contrary to the name.
      
      Change --suppress-cc=sob to mean only SOB lines, and add separate
      choices 'bodycc' (body Cc lines) and 'body' (both 'sob' and 'bodycc').
      The option --no-signed-off-by-cc now acts like --suppress-cc=sob,
      which is not backwards compatible but matches the name of the option.
      
      Also update the documentation and add a few tests.
      
      Original patch by me. Revised by Thomas Rast, who contributed the
      documentation and test updates.
      Signed-off-by: NJay Soffian <jaysoffian@gmail.com>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      3531e270
  7. 29 12月, 2008 1 次提交
  8. 28 12月, 2008 1 次提交
  9. 10 12月, 2008 1 次提交
  10. 12 11月, 2008 3 次提交
  11. 01 10月, 2008 7 次提交
  12. 01 9月, 2008 1 次提交
  13. 31 7月, 2008 1 次提交
  14. 02 7月, 2008 1 次提交
    • J
      Documentation: be consistent about "git-" versus "git " · b1889c36
      Jonathan Nieder 提交于
      Since the git-* commands are not installed in $(bindir), using
      "git-command <parameters>" in examples in the documentation is
      not a good idea. On the other hand, it is nice to be able to
      refer to each command using one hyphenated word. (There is no
      escaping it, anyway: man page names cannot have spaces in them.)
      
      This patch retains the dash in naming an operation, command,
      program, process, or action. Complete command lines that can
      be entered at a shell (i.e., without options omitted) are
      made to use the dashless form.
      
      The changes consist only of replacing some spaces with hyphens
      and vice versa. After a "s/ /-/g", the unpatched and patched
      versions are identical.
      Signed-off-by: NJonathan Nieder <jrnieder@uchicago.edu>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      b1889c36
  15. 26 6月, 2008 1 次提交
  16. 09 6月, 2008 1 次提交
    • S
      Docs: Use "-l::\n--long\n" format in OPTIONS sections · 3240240f
      Stephan Beyer 提交于
      The OPTIONS section of a documentation file contains a list
      of the options a git command accepts.
      
      Currently there are several variants to describe the case that
      different options (almost) do the same in the OPTIONS section.
      
      Some are:
      
       -f, --foo::
       -f|--foo::
       -f | --foo::
      
      But AsciiDoc has the special form:
      
       -f::
       --foo::
      
      This patch applies this form to the documentation of the whole git suite,
      and removes useless em-dash prevention, so \--foo becomes --foo.
      Signed-off-by: NStephan Beyer <s-beyer@gmx.net>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      3240240f
  17. 07 6月, 2008 1 次提交
  18. 20 3月, 2008 1 次提交
  19. 05 2月, 2008 2 次提交
    • D
      git-send-email: Generalize auto-cc recipient mechanism. · 65648283
      David Brown 提交于
      There are a few options to git-send-email to suppress the automatic
      generation of 'Cc' fields: --suppress-from, and --signed-off-cc.
      However, there are other times that git-send-email automatically
      includes Cc'd recipients.  This is not desirable for all development
      environments.
      
      Add a new option --suppress-cc, which can be specified one or more
      times to list the categories of auto-cc fields that should be
      suppressed.  If not specified, it defaults to values to give the same
      behavior as specified by --suppress-from, and --signed-off-cc.  The
      categories are:
      
        self   - patch sender.  Same as --suppress-from.
        author - patch author.
        cc     - cc lines mentioned in the patch.
        cccmd  - avoid running the cccmd.
        sob    - signed off by lines.
        all    - all non-explicit recipients
      Signed-off-by: NDavid Brown <git@davidb.org>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      65648283
    • M
      git-send-email: ssh/login style password requests · 2363d746
      Michael Witten 提交于
      Whilst convenient, it is most unwise to record passwords
      in any place but one's brain. Moreover, it is especially
      foolish to store them in configuration files, even with
      access permissions set accordingly.
      
      git-send-email has been amended, so that if it detects
      an smtp username without a password, it promptly prompts
      for the password and masks the input for privacy.
      
      Furthermore, the argument to --smtp-pass has been rendered
      optional.
      
      The documentation has been updated to reflect these changes.
      Signed-off-by: NMichael Witten <mfwitten@mit.edu>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      2363d746
  20. 27 1月, 2008 1 次提交
  21. 07 1月, 2008 1 次提交
    • D
      Documentation: rename gitlink macro to linkgit · 5162e697
      Dan McGee 提交于
      Between AsciiDoc 8.2.2 and 8.2.3, the following change was made to the stock
      Asciidoc configuration:
      
      @@ -149,7 +153,10 @@
       # Inline macros.
       # Backslash prefix required for escape processing.
       # (?s) re flag for line spanning.
      -(?su)[\\]?(?P<name>\w(\w|-)*?):(?P<target>\S*?)(\[(?P<attrlist>.*?)\])=
      +
      +# Explicit so they can be nested.
      +(?su)[\\]?(?P<name>(http|https|ftp|file|mailto|callto|image|link)):(?P<target>\S*?)(\[(?P<attrlist>.*?)\])=
      +
       # Anchor: [[[id]]]. Bibliographic anchor.
       (?su)[\\]?\[\[\[(?P<attrlist>[\w][\w-]*?)\]\]\]=anchor3
       # Anchor: [[id,xreflabel]]
      
      This default regex now matches explicit values, and unfortunately in this
      case gitlink was being matched by just 'link', causing the wrong inline
      macro template to be applied. By renaming the macro, we can avoid being
      matched by the wrong regex.
      Signed-off-by: NDan McGee <dpmcgee@gmail.com>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      5162e697
  22. 19 12月, 2007 1 次提交
  23. 08 11月, 2007 1 次提交
  24. 25 10月, 2007 1 次提交
  25. 27 9月, 2007 1 次提交
  26. 03 9月, 2007 1 次提交
    • D
      send-email: Add support for SSL and SMTP-AUTH · 34cc60ce
      Douglas Stockwell 提交于
      Allows username and password to be given using --smtp-user
      and --smtp-pass. SSL use is flagged by --smtp-ssl. These are
      backed by corresponding defaults in the git configuration file.
      
      This implements Junio's 'mail identity' suggestion in a slightly
      more generalised manner. --identity=$identity, backed by
      sendemail.identity indicates that the configuration subsection
      [sendemail "$identity"] should take priority over the [sendemail]
      section for all configuration values.
      Signed-off-by: NDouglas Stockwell <doug@11011.net>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      34cc60ce
  27. 20 8月, 2007 1 次提交
  28. 18 8月, 2007 2 次提交
  29. 20 7月, 2007 1 次提交
  30. 28 6月, 2007 1 次提交