linux-kernel - Re: [GIT PULL rcu/next] RCU commits for 3.20

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 10 Feb 2015 10:34:44 -0800
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	David Hildenbrand <dahi@...ux.vnet.ibm.com>
Cc:	Ingo Molnar <mingo@...nel.org>, linux-kernel@...r.kernel.org,
	Christian Ehrhardt <ehrhardt@...ux.vnet.ibm.com>,
	Heiko Carstens <heiko.carstens@...ibm.com>
Subject: Re: [GIT PULL rcu/next] RCU commits for 3.20

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@...r.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@...r.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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/