From: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Date: Mon, 09 Feb 2015 22:01:59 GMT
Subject: Re: Is there some way to suppress Cc email only to stable?
Message-ID: <20150209220159.GF4166@linux.vnet.ibm.com>
In-Reply-To: <xmqqpp9iahct.fsf@gitster.dls.corp.google.com>

On Mon, Feb 09, 2015 at 01:46:10PM -0800, Junio C Hamano wrote:
> "Paul E. McKenney" <paulmck@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 = stable@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
> > stable@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 stable@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?

Would it help if I offered a beer?  ;-)

							Thanx, Paul