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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
