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

Sending a threaded patch series with Evolution

From
Matt McCutchen <matt@mattmccutchen.net>
Date
Dec 14, 2008, 02:34 UTC
Message-ID
<1229222058.2838.22.camel@mattlaptop2.local>
In-Reply-To
<m3hc57g28b.fsf@localhost.localdomain>
On Sat, 2008-12-13 at 14:05 -0800, Jakub Narebski wrote: 
> By the way, your message [PATCH 2/2] should be threaded, i.e. be
> response to [PATCH 1/2] (or to cover letter [PATCH 0/2]), to not
> mistake it with other [PATCH 2/2] patches.

I'm using Evolution 2.24 as my mail client, and I have a wrapper script "git draft-patch" that runs "git format-patch" and loads the patches into my Evolution Drafts folder so I can look them over in the composer and add non-commit-message text below the "---" if I wish before sending. I did pass --thread, but the composer changed the Message-Id, breaking the threading.

I'll try to get this right in the future. I can see two approaches to doing so:

1. Check over / edit the patches in a text editor before loading them
into Drafts, and then send them by moving them directly to Outbox
(without using the composer) so that the Message-Id won't change.
2. Send the first patch, then manually edit the Message-Id Evolution
assigned it into the second patch, etc.

Neither of these approaches is particularly nice. Does anyone have a better idea?

-- 
Matt
Previous: Jakub NarebskiNext: Matt McCutchen
Message 4 of 7 in “gitweb: support hiding projects from user-visible lists”
  1. 2/2 gitweb: support hiding projects from user-visible listsMatt McCutchen, Dec 13, 2008
  2. Jakub NarebskiDec 13, 2008
  3. Jakub NarebskiDec 13, 2008
  4. Sending a threaded patch series with EvolutionMatt McCutchen, Dec 14, 2008
  5. Matt McCutchenDec 24, 2008
  6. Jakub NarebskiJan 2, 2009
  7. gitweb config with some public, some basic-authenticated reposMatt McCutchen, Jan 3, 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.