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:46:10 -0800 [thread overview]
Message-ID: <xmqqpp9iahct.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20150209214312.GC4166@linux.vnet.ibm.com> (Paul E. McKenney's message of "Mon, 9 Feb 2015 13:43:12 -0800")
"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?
next prev parent reply other threads:[~2015-02-09 21:46 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
2015-02-09 21:43 ` Paul E. McKenney
2015-02-09 21:46 ` Junio C Hamano [this message]
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=xmqqpp9iahct.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