From: Jay Soffian <jaysoffian@gmail.com>
To: John Tapsell <johnflux@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH 2/2] Google has renamed the imap folder
Date: Tue, 17 Feb 2009 12:45:17 -0500 [thread overview]
Message-ID: <76718490902170945s5c15228bn798fe6b7e0063da@mail.gmail.com> (raw)
In-Reply-To: <200902171045.05904.johnflux@gmail.com>
On Tue, Feb 17, 2009 at 5:45 AM, John Tapsell <johnflux@gmail.com> wrote:
> Also add a comment that the web interface wraps the lines
>
> Signed-off-by: John Tapsell <johnflux@gmail.com>
> ---
> Documentation/SubmittingPatches | 10 +++++++++-
> 1 files changed, 9 insertions(+), 1 deletions(-)
>
> diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
> index 9b559ad..aa41c9e 100644
> --- a/Documentation/SubmittingPatches
> +++ b/Documentation/SubmittingPatches
> @@ -491,12 +491,18 @@ message, complete the addressing and subject fields, and press send.
> Gmail
> -----
>
> +GMail does not appear to have any way to turn off line wrapping in the web
> +interface, so this will mangle any emails that you send. You can however
> +use any IMAP email client to connect to the google imap server, and forward
> +the emails through that. Just make sure to disable line wrapping in that
> +email client.
> +
> Submitting properly formatted patches via Gmail is simple now that
> IMAP support is available. First, edit your ~/.gitconfig to specify your
> account settings:
>
> [imap]
> - folder = "[Gmail]/Drafts"
> + folder = "[Google Mail]/Drafts"
> host = imaps://imap.gmail.com
> user = user@gmail.com
> pass = p4ssw0rd
Hmm, maybe just point users at send-email? It has SSL support built-in
now so it can trivially use gmail's SMTP servers and you need not
worry about mangling. So the only remaining reason to use the imap
kludge is so that you have access to your gmail address book for
filling in the To/Cc fields and the subject.
j.
next prev parent reply other threads:[~2009-02-17 17:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 10:45 [PATCH 2/2] Google has renamed the imap folder John Tapsell
2009-02-17 17:45 ` Jay Soffian [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-17 10:12 John Tapsell
2009-02-17 18:39 ` Junio C Hamano
2009-02-17 18:54 ` Shawn O. Pearce
2009-02-17 19:04 ` Sverre Rabbelier
2009-02-17 19:16 ` Shawn O. Pearce
2009-02-17 23:14 ` John Tapsell
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=76718490902170945s5c15228bn798fe6b7e0063da@mail.gmail.com \
--to=jaysoffian@gmail.com \
--cc=git@vger.kernel.org \
--cc=johnflux@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).