cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ugo Cei <>
Subject Re: [POLL] don't edit files just for style changes?
Date Sat, 17 Apr 2004 15:00:33 GMT
Il giorno 17/apr/04, alle 16:18, Bertrand Delacretaz ha scritto:

> I have three suggestions:
> 1) As a general rule, we should refrain from making such changes to 
> our code, unless there is a good reason (code change for example) to 
> edit the file in question.
> 2) When editing a file for a good reason, we should look for such 
> "style" problems and fix them at the same time, or as a separate 
> commit, but before testing our changes.
> 3) We should not change the indentation / code writing style (brackets 
> etc.) of a file when making a minor change to it.
> The idea is to keep the flow of CVS diff messages as low as possible, 
> to save our neuronal bandwidth for more important things than the 
> placement of brackets or the order of imports.
+ 1


View raw message