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)


On Oct 16, 2013, at 1:51 PM, Paulo J. Matos <paulo@matos-sorge.com> wrote:
> On 16/10/13 19:32, Mike Stump wrote:
>> 
>> Committed revision 203715.
> 
> Awesome!
> Can I backport your patch to 4_8?

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.

If you have your own private tree, you can also place it in your tree.  If you merely have a checkout, you can place it into your checkout.  This should get you 90% of the benefit.  Additionally, you can remove customizations from your environment that conflict with the style set in that file, and instead, bundle such a file with the projects that want a non-default style.  The default style works well with GNU software (as long as you don't edit .md files).

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