git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sverre Rabbelier <srabbelier@gmail.com>
To: Aaron Crane <git@aaroncrane.co.uk>
Cc: git@vger.kernel.org
Subject: Re: Gmail and unwanted line-wrapping
Date: Sat, 6 Feb 2010 21:47:39 +0100	[thread overview]
Message-ID: <fabb9a1e1002061247k7a8fba5at4c687faac0dcabb8@mail.gmail.com> (raw)
In-Reply-To: <bc341e101002061229t7a1525c2w2d5a8e221124b3c2@mail.gmail.com>

Heya,

On Sat, Feb 6, 2010 at 21:29, Aaron Crane <git@aaroncrane.co.uk> wrote:
> Can anyone think of anything I might have done wrong here?  If not,
> I'm inclined to suggest dropping all of that advice.  That's not
> ideal, because it leaves Gmail users with no obvious way to submit
> well-formatted patches to the list; but it's better than suggesting
> something which apparently doesn't work.

I'm using git send-email with this configuration:
[sendemail]
  smtencryption = tls
  smtpserver = smtp.gmai.com
  smtpuser = srabbelier@gmail.com
  smptserverport = 587

It'll ask you for your password when you're sending the emails. Like so:

$ git format-patch --no-color -C -M origin/master..topic-branch -o outgoing/
$ git send-email --compose outgoing/00*

Of course you should substitute specific things as appropriate, I
doubt you'll want to be sending your patches pretending to be me :P.

-- 
Cheers,

Sverre Rabbelier

  reply	other threads:[~2010-02-06 20:48 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 [this message]
2010-02-07  0:24   ` David Aguilar
2010-02-07  0:50     ` Jay Soffian
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=fabb9a1e1002061247k7a8fba5at4c687faac0dcabb8@mail.gmail.com \
    --to=srabbelier@gmail.com \
    --cc=git@aaroncrane.co.uk \
    --cc=git@vger.kernel.org \
    /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).