Re: [PATCH] Documentation/SubmittingPatches: Clarify Gmail section

From: Jon Seymour <jon.seymour@gmail.com>
Date: Apr 7, 2010, 22:23 UTC
Message-ID: <k2m2cfc40321004071523z8c036cccs12302a70f25bb413@mail.gmail.com>
In-Reply-To: <y2gf3271551004071318zb4ed7ef6o93a6c98c6009d8df@mail.gmail.com>

On Thu, Apr 8, 2010 at 6:18 AM, Ramkumar Ramachandra <artagnon@gmail.com> wrote:

Show 14 quoted lines

>> Is the web interface the _only_ way to interact with IMAP drafts on Gmail?
>> If that is the case, your patch (or Aaron's earlier attempt) to make the
>> document not to talk about imap-send in the context of Gmail makes sense.
>
> No. An email client can sync with the drafts folder in GMail over
> IMAP. However, sending the final email has to be done over SMTP.
> The effect of "git imap-send" can be replicated by copy-pasting text
> into the email client's compose interface. So, using "git imap-send"
> seems like a bit of a roundabout way to me. There are some usecases
> though (like queuing up patches as drafts before sending): so I'll add
> a paragraph about this in my next revision.
>
> -- Ram
> --

git imap-send has far less manual steps than cut and pasting into an e-mail client, so it is certainly preferable to cut-and-paste which seems particularly error prone.

Perhaps the words could be changed to something like:

If you do want to use the imap-send option with Gmail you MUST use an IMAP client that does not line wrap to do any final polishing of the patch e-mails prior to submitting them to the list. If you use the gmail web interface to edit the draft messages in any way, line wrapping WILL occur.

jon.