I realize it is easier to have standard way of working. But in the end that reduces once person's efforts by pushing them on to others.
I'm willing to compromise with proposal #2 which is to reformat in a separate commit. It will take an extra 2 minutes to do, but will save much more for the person coming after.
And BTW, turning off the auto-reformat on save, is a lot easier than spending an hour merging code. You could even write an EASE script to add a button to toggle the reformatter (if that doesn't exist already).
From: cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on behalf of Doug Schaefer [cdtdoug@xxxxxxxxx]
Sent: March 15, 2016 11:13 AM
To: CDT General developers list.
Subject: Re: [cdt-dev] Reformatting of code
I work on several projects. CDT is only one of them. I'd prefer not to have per project requirements for this. It's too hard to keep straight.
I also have format on save turned on to make sure I format all the code I touch. I recommend everyone do the same and use the default Java formatter. Then this will be less of an issue over time as we get all or code formatted the same.
Doug.