On Fri, May 22, 2015 at 1:49 PM, Thierry Reding <thierry.reding@xxxxxxxxx> wrote: > On Fri, May 22, 2015 at 12:33:42PM +0200, Arnd Bergmann wrote: >> On Friday 22 May 2015 12:00:03 Thierry Reding wrote: >> > >> > > Remember, if I have to hand-edit, or do something special with your >> > > patch, I will not do it, you need to do it correctly to make >> > > maintainer's lives easier, not harder, given that maintainers are the >> > > limited resouce, not developers. >> > >> > I understand. I'll make a mental note to never send you patches as >> > attachment again. >> > >> >> Better make that a general rule. My workflow is different from Greg's >> but also doesn't cope well with attachments. A lot of people in turn >> have problems quoting from an attachment when replying to the patch, >> which happens to work for me. > > Okay. Any hints on how to simplify sending out such patches with the > same list of recipients? I find it very annoying to have to manually > copy each recipient into the git send-email command-line, but I don't > know of a better way to do it. Replying to an email from the MUA will > at least do that automatically. You can write your recipients to the "To:" header of the patch you generated using git format-patch. git send-email will pick all recipients thus specified up automatically. In later iterations you can just copy the "To:" line. -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
