From: Junio C Hamano <hidden> Date: 2016-06-15 22:48:34
Ramkumar Ramachandra [off-list ref] writes:
The web interface mangles patches no matter what. Replace paragraph
about "git imap-send" with another one about "git send-email".
My impression has been that people are using MUAs that do not corrupt
patches and are capable of using IMAP drafts folders with Gmail, without
ever touching their patch-breaking web interface, and the description you
removed was meant for them.
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.
Even if it were not the case, as long as only very few people use IMAP
drafts on Gmail via MUAs not their web interface, I am fine with your
change to add send-email recipe to help Gmail users.
+GMail does not have any way to turn off line wrapping in the web
+interface, so this will mangle any emails that you send. You can
+either configure an email client that that doesn't break lines to use
+the GMail SMTP server, or use "git send-email" to achieve the same
+effect.
+
+To use "git send-email", edit ~/.gitconfig to specify your account
+settings:
+
+[sendemail]
+ smtpencryption = tls
+ smtpserver = smtp.gmail.com
+ smtpuser = user@gmail.com
+ smtppass = p4ssw0rd
+ smtpserverport = 587
+
+Once your commits are ready to send to the mailing list, run the
+following commands:
+
+ $ git format-patch --no-color -C -M origin/master -o outgoing/
+ $ git send-email --compose outgoing/*
From: Jacob Helwig <hidden> Date: 2016-06-15 22:48:34
On Wed, Apr 7, 2010 at 13:02, Junio C Hamano [off-list ref] wrote:
My impression has been that people are using MUAs that do not corrupt
patches and are capable of using IMAP drafts folders with Gmail, without
ever touching their patch-breaking web interface, and the description you
removed was meant for them.
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.
The web interface isn't the only way. I use the IMAP drafs all the
time with mutt, and most mutt + gmail instructions I've seen online
setup this behavior.
Even if it were not the case, as long as only very few people use IMAP
drafts on Gmail via MUAs not their web interface, I am fine with your
change to add send-email recipe to help Gmail users.
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
From: Jon Seymour <hidden> Date: 2016-06-15 22:48:34
On Thu, Apr 8, 2010 at 6:18 AM, Ramkumar Ramachandra [off-list ref] wrote:
quoted
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.