From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: David Hildenbrand <dahi@linux.vnet.ibm.com>
Cc: Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org,
Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>
Subject: Re: [GIT PULL rcu/next] RCU commits for 3.20
Date: Tue, 10 Feb 2015 10:34:44 -0800 [thread overview]
Message-ID: <20150210183444.GT4166@linux.vnet.ibm.com> (raw)
In-Reply-To: <20150210091948.41d5b58b@thinkpad-w530>
On Tue, Feb 10, 2015 at 09:19:48AM +0100, David Hildenbrand wrote:
> > > OK, so if I understand correctly, I need to add the Cc:
> > > stable tags after the last
> > > git-format-patch/git-send-email, but (of course) before
> > > the git-request-pull. Is that the trick?
> >
> > So I'd try to avoid the unnecessary rebase: teach
> > git-send-email to not Cc: to -stable, even though it's in
> > the Cc: list? Not sure how that's done though.
> >
>
> --suppress-cc=stable@vger.kernel.org ?
>
> or as an alternative
>
> --suppress-cc=bodycc
>
> Maybe that's what you're looking for.
It wasn't obvious from the documentation that placing the email address
in "--suppress-cc=stable@vger.kernel.org" would work. However, Greg KH
says that it is OK to Cc stable -- apparently the gripe-mail I got some
time back when doing this was an anomaly.
Thanx, Paul
prev parent reply other threads:[~2015-02-10 18:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 0:45 Paul E. McKenney
2015-01-21 5:15 ` Ingo Molnar
2015-02-03 14:34 ` David Hildenbrand
2015-02-03 16:34 ` Paul E. McKenney
2015-02-06 18:28 ` Ingo Molnar
2015-02-06 18:56 ` Paul E. McKenney
2015-02-09 7:56 ` Ingo Molnar
2015-02-09 13:50 ` Paul E. McKenney
2015-02-09 17:45 ` Ingo Molnar
2015-02-09 19:43 ` Paul E. McKenney
2015-02-10 8:19 ` David Hildenbrand
2015-02-10 18:34 ` Paul E. McKenney [this message]
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=20150210183444.GT4166@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=dahi@linux.vnet.ibm.com \
--cc=ehrhardt@linux.vnet.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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
Powered by JetHome