Re: [PATCH] Documentation/SubmittingPatches: fix Gmail workaround advice
- From
- Aaron Crane <git@aaroncrane.co.uk>
- Date
- Feb 7, 2010, 20:03 UTC
- Message-ID
- <bc341e101002071203x52bceaach8d42c6188630f1d1@mail.gmail.com>
- In-Reply-To
- <7v8wb4gaef.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> wrote:
Show 8 quoted lines
> Aaron Crane <git@aaroncrane.co.uk> writes: >> The suggested approach to dealing with Gmail's propensity for breaking >> patches doesn't seem to work. Recommend an alternative technique which >> does. > > Do you know _why_ it does not work? For example, does it not work _at > all_ for you? Or only certain things does not reliably work (iow, perhaps > you are seeing a bug in imap-send)?
What happens for me is that `git imap-send` successfully puts the message into the gmail Drafts folder, but when it's sent it's been line-wrapped (and any line-end spaces are deleted, which breaks diffs containing empty context lines).
I've verified that it's not `git imap-send` at fault, by tweaking it to tee all socket-written data to a local file; all whitespace in the mail prepared locally is sent to Gmail unchanged. So Gmail is mangling the message when it gets uploaded (or possibly when it's opened in the web interface, or when it's sent).
I've tried this both with a vanilla Gmail account, and with Google Apps For Your Domain Standard Edition, and I get the same behaviour.
> 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.
-- Aaron Crane ** http://aaroncrane.co.uk/