git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jay Soffian <jaysoffian@gmail.com>
To: David Aguilar <davvid@gmail.com>
Cc: Sverre Rabbelier <srabbelier@gmail.com>,
	Aaron Crane <git@aaroncrane.co.uk>,
	git@vger.kernel.org
Subject: Re: Gmail and unwanted line-wrapping
Date: Sat, 6 Feb 2010 19:50:35 -0500	[thread overview]
Message-ID: <76718491002061650ge299426s22de5e00b26af108@mail.gmail.com> (raw)
In-Reply-To: <20100207002413.GA14744@gmail.com>

> I've added it to the Git Wiki:
> http://git.wiki.kernel.org/index.php/GitTips#Using_gmail_to_send_your_patches

If you're on MacOS X and have MacPorts installed, then install both
the curl and msmtp packages, then use an .msmtprc as follows:

defaults
tls on
tls_trust_file /opt/local/share/curl/curl-ca-bundle.crt
syslog LOG_MAIL

# gmail
account gmail
host smtp.gmail.com
port 587
auth on
from jaysoffian@gmail.com
user jaysoffian@gmail.com

# Default account
account default : gmail

Adjusting for you account of course. And in your git config:

[sendemail]
	smtpserver = /opt/local/bin/msmtp


Now why would you do this you ask instead of using git's built-in SMTP
support? Because I provided a patch to msmtp long ago that lets it
access your gmail password from Mac OS X's keychain. Note that it
looks for a password stored in the same format as Mail.app would store
it, see the msmtp man page for details.

FWIW, I think Gnome also has a keychain like thingy that msmtp can also query.

j.

  reply	other threads:[~2010-02-07  0:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-06 20:29 Gmail and unwanted line-wrapping Aaron Crane
2010-02-06 20:47 ` Sverre Rabbelier
2010-02-07  0:24   ` David Aguilar
2010-02-07  0:50     ` Jay Soffian [this message]
2010-02-07  0:51       ` Jay Soffian
2010-02-08 15:20       ` Erik Faye-Lund
2010-02-06 20:49 ` Jacob Helwig
2010-02-06 20:59   ` Sverre Rabbelier

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=76718491002061650ge299426s22de5e00b26af108@mail.gmail.com \
    --to=jaysoffian@gmail.com \
    --cc=davvid@gmail.com \
    --cc=git@aaroncrane.co.uk \
    --cc=git@vger.kernel.org \
    --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).