From: Sverre Rabbelier <srabbelier@gmail.com>
To: Jacob Helwig <jacob.helwig@gmail.com>
Cc: Aaron Crane <git@aaroncrane.co.uk>, git@vger.kernel.org
Subject: Re: Gmail and unwanted line-wrapping
Date: Sat, 6 Feb 2010 21:59:39 +0100 [thread overview]
Message-ID: <fabb9a1e1002061259t78d3239dmdbe78d5136db8fab@mail.gmail.com> (raw)
In-Reply-To: <20100206204917.GA30894@vfb-9.home>
Heya,
On Sat, Feb 6, 2010 at 21:49, Jacob Helwig <jacob.helwig@gmail.com> wrote:
> I don't get the handy address-book of the web interface, but I don't
> have to worry about line-wrapping.
I get both using the magic awesomeness that is copy/paste. (Figure out
who to mail in web interface, then copy/paste To: line to cmdline)
--
Cheers,
Sverre Rabbelier
prev parent reply other threads:[~2010-02-06 21:00 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
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 [this message]
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=fabb9a1e1002061259t78d3239dmdbe78d5136db8fab@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=git@aaroncrane.co.uk \
--cc=git@vger.kernel.org \
--cc=jacob.helwig@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).