git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Documentation/SubmittingPatches: fix Gmail workaround advice

From
Jay Soffian <jaysoffian@gmail.com>
Date
Feb 7, 2010, 18:01 UTC
Message-ID
<76718491002071001l7dee7c4fr64cf2e57072b184@mail.gmail.com>
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:
Show 6 quoted lines
> 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.
Previous: Aaron CraneNext: Junio C Hamano
Message 2 of 7 in “Documentation/SubmittingPatches: fix Gmail workaround advice”
  1. Documentation/SubmittingPatches: fix Gmail workaround adviceAaron Crane, Feb 7, 2010
  2. Jay SoffianFeb 7, 2010
  3. Junio C HamanoFeb 7, 2010
  4. Aaron CraneFeb 7, 2010
  5. Jonathan NiederFeb 7, 2010
  6. Jonathan NiederFeb 7, 2010
  7. Junio C HamanoFeb 8, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.