Jeff King <peff@xxxxxxxx> writes: > On Thu, Apr 05, 2012 at 11:55:18PM -0700, Junio C Hamano wrote: > ... > I've played with that workflow before. While it's a neat trick, note > that something like "format-patch -s" will put the signoff at the end, > like: > > commit subject > > commit body > --- > Cc: whomever > Signed-off-by: you > > which is not what you want. Well, then "don't do it then". The reason the Cc: was abused in this thread originally is about recording the people who reviewed, so you are doing an amend of an existing commit in an editor. Why wouldn't the commit that was already reviewed at least once didn't have S-o-b in the first place? In other words, isn't the "-s" option in "format-patch" a useless feature creep that would only help those with broken workflows? > About a year ago I had an RFC series to let "git commit" parse off the > "---" bit and turn it into a git-note ... > ... Ultimately I didn't follow up because > I've found that I just don't end up keeping a lot of notes. I tend to do > the re-roll and then send it out pretty soon afterward, so I just write > any notes in the emails as they go out. > > For complex "cc" lists and the like, I have a (fairly hacky) script that > takes an existing message as input and generates a format-patch series > with the to, cc, and in-reply-to fields filled in (and then I ship the > result out via my regular MUA after proof-reading and tweaking). > Potentially git-send-email could do the same thing. Perhaps. -- 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