From: Junio C Hamano <gitster@pobox•com>
To: "Paul E. McKenney" <paulmck@linux•vnet.ibm.com>
Cc: git@vger•kernel.org, mingo@kernel•org
Subject: Re: Is there some way to suppress Cc email only to stable?
Date: Mon, 09 Feb 2015 13:17:05 -0800 [thread overview]
Message-ID: <xmqqtwyuaipa.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20150209211021.GB4166@linux.vnet.ibm.com> (Paul E. McKenney's message of "Mon, 9 Feb 2015 13:10:21 -0800")
"Paul E. McKenney" <paulmck@linux•vnet.ibm.com> writes:
> On Mon, Feb 09, 2015 at 12:57:11PM -0800, Junio C Hamano wrote:
>> No, I do not think we have a way to blacklist certain recipient
>> addresses from getting passed to the MTA, and I do not object to
>> addition of such a mechanism if there is a valid need to do so.
>>
>> It feels a bit too convoluted to say "Cc: to this address" in the
>> log message and then "nonono, I do not want to send there", though.
>> Why do you want to have Cc: in the log message if you do not want to
>> send e-mail to that address in the first place? Allowing the
>> behaviour you are asking for would mean that those who see that the
>> commit appeared on a branch would not be able to assume that the
>> patch has already been sent to the stable review address, no?
>
> I could see where it might seem a bit strange. ;-)
>
> The reason behind this is that you are not supposed to actually send
> email to the stable lists until after the patch has been accepted into
> mainline. One way to make this work is of course to leave the stable
> Cc tags out of the commit log, and to manually send an email when the
> commit has been accepted. However, this is subject to human error,
> and more specifically in this case, -my- human error.
>
> 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?
Or is it that nobody actually sends to stable@vger•kernel.org address
manually, but some automated process scans new commits that hit the
mainline and the string "Cc: stable@vger•kernel.org" is used as a cue
for that process to pick them up?
next prev parent reply other threads:[~2015-02-09 21:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-09 19:42 Is there some way to suppress Cc email only to stable? Paul E. McKenney
2015-02-09 20:57 ` Junio C Hamano
2015-02-09 21:10 ` Paul E. McKenney
2015-02-09 21:17 ` Junio C Hamano [this message]
2015-02-09 21:43 ` Paul E. McKenney
2015-02-09 21:46 ` Junio C Hamano
2015-02-09 22:01 ` Paul E. McKenney
2015-02-09 21:53 ` Jonathan Nieder
2015-02-09 23:35 ` Paul E. McKenney
2015-02-10 0:03 ` Greg KH
2015-02-10 0:35 ` Paul E. McKenney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqtwyuaipa.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=mingo@kernel$(echo .)org \
--cc=paulmck@linux$(echo .)vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox