> -----Original Message----- > From: Simon Oosthoek > Sent: Wednesday, December 26, 2012 4:08 PM > > * Junio C Hamano <gits...@pobox.com> [2012-12-26 12:35:28 -0800]: > > > > > > Anyway, I could imagine this as optional flag of git format-patch, > so you could say: > > > $ git format-patch -s --in-reply-to-email <mboxfile> a7fe7de8
Anyway you would need a --in-reply-to-email and a --in-reply-to-all-email, both should support stdin. Then you can feel free to --[no-]to and --[no-]cc (where is the --bcc?) to your heart's content. It would be a nice addition. > > > > > > But I'll save that as an exercise for the reader (or the future) > > > > I think a much more general approach would be to turn your script > > into "get-msg-id" script and use it like so: > > > > $ git format-patch --in-reply-to $(get-msg-id <mboxfile>) a7fe7de8 > > > > Then you can reuse that script in a context outside format-patch, > > whereever you need the message-id in a single message in the > > mailbox. > > > > That would work for the message-ID, but not for the various To: and Cc: > addresses. > > The hacky script that I sent afterwards produces a string with the Nit, it does not make use of the reply-to header if present. > various options to git format-patch (--to --cc --in-reply-to) based on > the headers To:/Cc:/From:/Message-ID: > > Cheers > > Simon > -- > To unsubscribe from this list: send the line "unsubscribe git" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html
smime.p7s
Description: S/MIME cryptographic signature
