It is a nuisance that the emails for a patch series have to be hand-edited after they are generated by "git format-patch". Some of the problems with this workflow are 1. The extra information typed into the email series is not archived in the git repository, and therefore the emails have to be kept around. 2. If it is discovered between "git format-patch" and "git send-email" that one of the patches needs a tweak, then the email series has to be generated anew and all of the hand-edits need to be redone. 3. If a "v2" of the patch series has to be created, all of the hand-edits have to be done again. 4. There is no place to store the "additional information" (the part that comes in patch emails between the "---" and the diffstat) while working on the patch series; it all has to be remembered or noted somewhere else until just before sending off the patch emails. Wouldn't it be nice if more of the information needed by "git format-patch" could be extracted from the git repository? For example: * The subject and body of the cover letter could be written to the log message of an annotated tag at the tip of the patch series. "git format-patch" could retrieve it if the "--cover-letter" option is used. * The CC and ACK lists could be written as specially-formatted lines in the annotated tag's log message, or perhaps in a git note. * The "additional information" could be written to git notes. I don't know whether git notes are the right vessel for such information. For example, are they carried along when a commit is rebased? I don't have time to implement any of this, but perhaps somebody thinks this is a good idea and is inspired to work on it. Michael -- Michael Haggerty mhagger@xxxxxxxxxxxx http://softwareswirl.blogspot.com/ -- 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