Re: [openstack-dev] Spam of patches (was: [trove][neutron][cinder][swift][ceilometer][nova][keystone][sahara][glance][neutron-lbaas][imm] stylistic changes to code, how do we handle them?)

2016-01-20 Thread Mike Perez
On 15:32 Jan 12, Julien Danjou wrote: > On Tue, Jan 12 2016, Amrith Kumar wrote: > > > My question to the ML is this, should stylistic changes of this kind be > > handled > > in a consistent way across all projects, maybe with a hacking rule and some > > discussion on the ML first? After all, if

[openstack-dev] Spam of patches (was: [trove][neutron][cinder][swift][ceilometer][nova][keystone][sahara][glance][neutron-lbaas][imm] stylistic changes to code, how do we handle them?)

2016-01-12 Thread Julien Danjou
On Tue, Jan 12 2016, Amrith Kumar wrote: > My question to the ML is this, should stylistic changes of this kind be > handled > in a consistent way across all projects, maybe with a hacking rule and some > discussion on the ML first? After all, if this change is worthwhile, it is > worth ensuring

Re: [openstack-dev] Spam of patches

2016-01-12 Thread Eric Harney
On 01/12/2016 09:32 AM, Julien Danjou wrote: > On Tue, Jan 12 2016, Amrith Kumar wrote: > >> My question to the ML is this, should stylistic changes of this kind be >> handled >> in a consistent way across all projects, maybe with a hacking rule and some >> discussion on the ML first? After all,

Re: [openstack-dev] Spam of patches

2016-01-12 Thread Anita Kuno
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/12/2016 09:32 AM, Julien Danjou wrote: > On Tue, Jan 12 2016, Amrith Kumar wrote: > >> My question to the ML is this, should stylistic changes of this >> kind be handled in a consistent way across all projects, maybe >> with a hacking rule and