This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Teaching emacs about GCC coding conventions (was Re: [PATCH] tree_code_name wrapper)


> -----Original Message-----
> From: gcc-patches-owner@gcc.gnu.org [mailto:gcc-patches-owner@gcc.gnu.org] On
> Behalf Of Mike Stump
> Sent: 16 October 2013 23:06
> To: Paulo J.Matos
> Cc: gcc-patches@gcc.gnu.org
> Subject: Re: Teaching emacs about GCC coding conventions (was Re: [PATCH]
> tree_code_name wrapper)
> 
> First, we like to wait and let patches bake on mainline before considering back
> porting, this has no bake time yet in our tree.  Second, only patches that impact
> quality enough should be back ported.  I tend to think that this one does not
> impact quality enough to worry about.  Also, you should develop on trunk, not
> 4_8.  Arguably, I would say no.  Now, a release manager can always review approve
> it; it should be very, very low risk.
> 

Makes sense. Thanks for the clarification.

-- 
Paulo Matos

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]