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

Re: Automatically filling in git send-email arguments based on an existing e-mail

From
John Keeping <john@keeping.me.uk>
Date
Oct 2, 2013, 10:19 UTC
Message-ID
<20131002101930.GH27238@serenity.lan>
In-Reply-To
<20131002082525.GU10217@login.drsnuggles.stderr.nl>
On Wed, Oct 02, 2013 at 10:25:25AM +0200, Matthijs Kooijman wrote:
Show 18 quoted lines
> sometimes when I send a patch, I want to reply it to an existing e-mail,
> using pretty much the same recipient list. Currently, I have to:
> 
>  - copy-paste the message id for --in-reply-to header
>  - copy one address for --to
>  - copy the other addresses for the --cc's
> 
> Since I can't just chuck a list of addresses into --cc and I need to
> quote every one because of the <> and spaces in there, this feels like
> it's more tedious than needed.
> 
> It seems like there should be a weay to just copy paste the headers from
> the original e-mail into the stdin of git send-email or a wrapper script
> and let it sort things out from there.
> 
> 
> Is there any interest in something like this? Does anyone else perhaps
> already have such a script lying around?

I have been working on this for a while, but haven't yet got anything into a suitable state for submission (and haven't made progress on it for a while). My WIP is at:

    https://github.com/johnkeeping/git/tree/format-patch-msgstore

The idea is to introduce a new helper protocol so that you can implement various ways of finding a message given a message-id; I've implemented one that finds the message from gmane.

What's there works in format-patch but not with send-email, which implements message IDs itself rather than forwarding the arguments to format-patch and I haven't had time to investigate changing send-email to work with these patches.

Previous: Matthijs Kooijman
Message 2 of 2 in “Automatically filling in git send-email arguments based on an existing e-mail”
  1. Matthijs KooijmanOct 2, 2013
  2. John KeepingOct 2, 2013

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.