On 12/1/05, Dmitry Beransky <db01@dembel.org> wrote:
> With modern IDEs that can change a file's coding style at a press of a
> button, shoehorning a programmer's habits into some arbitrary standard made
> no sense to me. So when I set up the development process for our group, I
> made a decision not to enforce any particular style and let my coders
> choose what works best for them. Unfortunately, and very understandably,
> this practice wreaks havoc when it comes to Subversion's diffs. Is there a
> good solution to this? Maybe a way to normalize the code before it's
> committed or diff is run? To make things more complicated we access
> Subversion via TortoiseSVN and IntelliJ IDEA.
While I dislike to be forced to a coding style different to my own,
whenever a group works at a bigger project, there has to be an
agreement about the style to be used. Because in my eyes the only
thing worse than an unloved coding style is a random mix of coding
styles.
So for project management reasons and of course svn's proper working,
I would recommend to have a standard setting for the autoindenters -
using them won't then result in a whole-file diff.
Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Dec 1 21:43:16 2005