git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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
Previous: Aaron CraneNext: Jonathan Nieder
Message 5 of 7 in “Documentation/SubmittingPatches: fix Gmail workaround advice”
  1. Documentation/SubmittingPatches: fix Gmail workaround adviceAaron Crane, Feb 7, 2010
  2. Jay SoffianFeb 7, 2010
  3. Junio C HamanoFeb 7, 2010
  4. Aaron CraneFeb 7, 2010
  5. Jonathan NiederFeb 7, 2010
  6. Jonathan NiederFeb 7, 2010
  7. Junio C HamanoFeb 8, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.