On 2/28/2011 2:02 AM, Gabor Szabo wrote: > > so far we were encouraging real code changes and tidying Padre > to be in separate commits. I was wondering if it would not be better > to encourage people to run tidy before every commit?
The key is to standardize on a Padre code format. One based on tidy could work but you need to specify the full configuration settings/prefs used for Padre. Ideally, running tidy over the same code twice would not change anything the 2nd run... > If we do that constantly then every tidy should only clean up our > own code change as the rest of Padre should be already tidy. > This means our diffs are still clean. I've run into this where a simple change is masked by 100's of lines of reformatting. It makes it very difficult to follow development changes or to debug any problems introduces or partially solved. > To further enhance this I am thinking to write a bot that after > every commit it would check out the latest version, run tidy > and if there were changes would commit them back. What do other large projects to in this respect? > This will eliminate big changes to the code base that are only tidying. A very good idea if standardized. --Chris _______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
