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

git-send-email: Support for Reply-To

From
Christian Ludwig <chrissicool@gmail.com>
Date
Mar 3, 2018, 23:58 UTC
Message-ID
<20180303235814.7241-1-chrissicool@gmail.com>
Hi,

this is the third iteration of this series. There was a request to rebase the changes on the refactoring patch b6049542 ("send-email: extract email-parsing code into a subroutine", 2017-12-15). This is the result.

The diffstat is the same compared to the last revision. It could be made smaller by sacrificing readibility and breaking the scheme introduced by the refactoring patch. But I do agree that send-email's readability could benefit from slicing it into handy functions. And the refactoring patch reduces the nesting of loops/conditionals.

But it's your code, you decide. I can re-send a fixed-up v2 without the rebasing.

So long,
 - Christian
Next: Christian Ludwig
Message 1 of 4 in “git-send-email: Support for Reply-To”
  1. Christian LudwigMar 3, 2018
  2. 1/2 send-email: Rename variable for clarityChristian Ludwig, Mar 3, 2018
  3. 2/2 send-email: Support separate Reply-To addressChristian Ludwig, Mar 3, 2018
  4. Junio C HamanoMar 6, 2018

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.