Re: [PATCH] Documentation/SubmittingPatches: fix Gmail workaround advice
- From
Jonathan Nieder <jrnieder@gmail.com>
- Date
- Feb 7, 2010, 21:54 UTC
- Message-ID
- <20100207215311.GA2177@progeny.tock>
- In-Reply-To
- <bc341e101002071203x52bceaach8d42c6188630f1d1@mail.gmail.com>
Aaron Crane wrote:
> Junio C Hamano <gitster@pobox.com> wrote:
Show 7 quoted lines
>> What I am trying to get at is to see if the current imap-send suggestion >> is fundamentally unworkable with gmail. Perhaps they stopped supporting >> imap. Perhaps the procedure never worked. > > As far as I can determine, the current imap-send suggestion is > fundamentally unworkable with gmail at the moment. I don't know > whether it ever used to work, though I've been assuming that it did.
I think it still works, or depending on your perspective, it never did. As John Tapsell wrote in SubmittingPatches (commit 50dffd4e, 2009-02-19):
| 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. Alternatively, use "git send-email" instead.
I am not sure what that means about what SubmittingPatches should say: should it explain both methods, then?
If I were doing it, I would put the information in the git-imap-send and git-send-mail man pages as examples. That way, it would be visible for people submitting patches to _other_ projects, too. The section in Documentation/SubmittingPatches could be replaced with a pointer.
Jonathan