git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jay Soffian <jaysoffian@gmail.com>
To: Aaron Crane <git@aaroncrane.co.uk>
Cc: git@vger.kernel.org, Sverre Rabbelier <srabbelier@gmail.com>,
	Jacob Helwig <jacob.helwig@gmail.com>,
	David Aguilar <davvid@gmail.com>
Subject: Re: [PATCH] Documentation/SubmittingPatches: fix Gmail workaround  advice
Date: Sun, 7 Feb 2010 13:01:13 -0500	[thread overview]
Message-ID: <76718491002071001l7dee7c4fr64cf2e57072b184@mail.gmail.com> (raw)
In-Reply-To: <1265555642-40204-1-git-send-email-git@aaroncrane.co.uk>

On Sun, Feb 7, 2010 at 10:14 AM, Aaron Crane <git@aaroncrane.co.uk> wrote:
> The suggested approach to dealing with Gmail's propensity for breaking
> patches doesn't seem to work.  Recommend an alternative technique which
> does.
>
> Signed-off-by: Aaron Crane <git@aaroncrane.co.uk>
> ---

Thanks for writing this up. See inline.

> +However, "git send-email" needs the Net::SMTP::SSL Perl module to send to
> +TLS-encrypted servers.  On some operating systems (like Mac OS X with
> +MacPorts), it may be hard to install that module.  In such cases, the
> +third-party "msmtp" program might be easier to install.

Neither is harder to install than the other, I use msmtp primarily for
historical reasons (git didn't used to support SMTP over SSL/TLS) and
because it doesn't prompt me for my password. :-)

So I'd just say:

"Note that "git send-email" needs the Net::SMTP::SSL Perl module to
send to TLS-encrypted servers.  Alternately, git can make use of the
third-party "msmtp" program like so:"

Thanks,

j.

  reply	other threads:[~2010-02-07 18:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-07 15:14 [PATCH] Documentation/SubmittingPatches: fix Gmail workaround advice Aaron Crane
2010-02-07 18:01 ` Jay Soffian [this message]
2010-02-07 18:37 ` Junio C Hamano
2010-02-07 20:03   ` Aaron Crane
2010-02-07 21:54     ` Jonathan Nieder
2010-02-07 22:16       ` Jonathan Nieder
2010-02-08 17:42         ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=76718491002071001l7dee7c4fr64cf2e57072b184@mail.gmail.com \
    --to=jaysoffian@gmail.com \
    --cc=davvid@gmail.com \
    --cc=git@aaroncrane.co.uk \
    --cc=git@vger.kernel.org \
    --cc=jacob.helwig@gmail.com \
    --cc=srabbelier@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).