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

Re: RFC re Thunderbird + imap-send

From
Jeremy White <jwhite@codeweavers.com>
Date
Feb 10, 2009, 19:00 UTC
Message-ID
<4991CEE9.8040402@codeweavers.com>
In-Reply-To
<49915FB6.8010803@drmicha.warpmail.net>
> Looks okay here. I leave the tarring and feathering to Dscho ;)
Thanks.
Show 5 quoted lines
> 
> Trying this out showed that indeed git-imap-send needs much more love.
> The man page doesn't say much, doesn't describe all options. Most
> options can be specified in config only. You can't pass file arguments,
> only stdin. You can't even pass a recipient!

Hmm. I think the documentation/man page is correct, at least in the tip; Rob Shearman fixed it back in July.

I think your larger concerns about git-imap-send are valid; it does seem that having two paths for emailing patches is less than ideal.

But I'm going to cowardly claim that is outside of my scope at this point. (I like starting flame wars and all, but adding --html to git-send-email just seems like a poor choice for my health <grin>).

Cheers,
Jeremy
Previous: Jeremy White
Message 5 of 5 in “RFC re Thunderbird + imap-send”
  1. Jeremy WhiteFeb 9, 2009
  2. Michael J GruberFeb 10, 2009
  3. Ben BuckschFeb 10, 2009
  4. Jeremy WhiteFeb 10, 2009
  5. Jeremy WhiteFeb 10, 2009

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.