"Paul E. McKenney" <paul...@linux.vnet.ibm.com> writes: >> > Hence the desire to have a Cc that doesn't actually send any email, >> > but that is visible in mainline for the benefit of the scripts that >> > handle the stable workflow. >> >> So a configuration variable that you can set once and forget, e.g. >> >> [sendemail] >> blacklistedRecipients = sta...@vger.kernel.org >> >> would not cut it, as you would _later_ want to send the e-mail once >> the commit hits the mainline. Am I reading you correctly? > > This would actually work for me. Once the patch is accepted into > mainline, I am done with it. So I should -never- send email to > sta...@vger.kernel.org, unless I am doing so manually, for example because > I forgot to add the stable tag to a given commit. But in that case, > I would just use mutt to forward the patch to sta...@vger.kernel.org, > and git would not be involved.
OK, thanks, we have a workable design to let us move forward, then. Gits, any takers? -- 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
