Re: [openstack-dev] [fuel] Unrelated changes in patches

2016-04-04 Thread Dmitry Borodaenko
On Mon, Apr 04, 2016 at 04:05:28PM +0300, Matthew Mosesohn wrote: > I've seen several cases where core reviewers bully contributors into > refactoring a particular piece of logic because it contains common > lines relating to some non-ideal code, even if the change doesn't > relate to this logic.

Re: [openstack-dev] [fuel] Unrelated changes in patches

2016-04-04 Thread Igor Kalnitsky
Dmitry Guryanov wrote: > It's often not so easy to decide, if you should include some unrelated > changes to your patch, like fixing spaces, renaming variables or > something else, which don't change logic. I'd say it depends. If, for example, variable name is used inside one function - it's ok

Re: [openstack-dev] [fuel] Unrelated changes in patches

2016-04-04 Thread Jason Rist
On 04/04/2016 07:05 AM, Matthew Mosesohn wrote: > Hi Dmitry, > > I've seen several cases where core reviewers bully contributors into > refactoring a particular piece of logic because it contains common > lines relating to some non-ideal code, even if the change doesn't > relate to this logic. >

Re: [openstack-dev] [fuel] Unrelated changes in patches

2016-04-04 Thread Matthew Mosesohn
Hi Dmitry, I've seen several cases where core reviewers bully contributors into refactoring a particular piece of logic because it contains common lines relating to some non-ideal code, even if the change doesn't relate to this logic. In general, I'm ok with formatting issues, but changing how a

[openstack-dev] [fuel] Unrelated changes in patches

2016-04-04 Thread Dmitry Guryanov
Hello, colleagues! It's often not so easy to decide, if you should include some unrelated changes to your patch, like fixing spaces, renaming variables or something else, which don't change logic. On the one hand you see something's wrong with the code and you'd like to fix it, on the other hand