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

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

From
Ramkumar Ramachandra <artagnon@gmail.com>
Date
Apr 7, 2010, 20:18 UTC
Message-ID
<y2gf3271551004071318zb4ed7ef6o93a6c98c6009d8df@mail.gmail.com>
In-Reply-To
<7vwrwjav4h.fsf@alter.siamese.dyndns.org>
> 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
Previous: Jacob HelwigNext: Jon Seymour
Message 5 of 7 in “Documentation/SubmittingPatches: Clarify Gmail section”
  1. Documentation/SubmittingPatches: Clarify Gmail sectionRamkumar Ramachandra, Apr 7, 2010
  2. Documentation/SubmittingPatches: Clarify Gmail sectionRamkumar Ramachandra, Apr 7, 2010
  3. Junio C HamanoApr 7, 2010
  4. Jacob HelwigApr 7, 2010
  5. Ramkumar RamachandraApr 7, 2010
  6. Jon SeymourApr 7, 2010
  7. Junio C HamanoApr 7, 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.