Re: coping with different coding styles

On Thursday 01 December 2005 18:15, Dmitry Beransky wrote:
[...]
> Commits isn't the only place where different coding style may become a
> problem. A diff between the working base and the working copy can also get
> screwed up by reformatted code.

For the diff issue: I suppose you could try to create a script that would
format the code back to whatever format you're using in the repository
itself, then call your regular diff utility command on the reformatted local
file and its repository version.

You'd then use this script with the --diff-cmd option to the svn diff command.
I dare say this would be fairly transparent to the user.

--
Cheers,
Adalberto
This communication is for use by the intended recipient and contains
information that may be Privileged, confidential or copyrighted under
applicable law. If you are not the intended recipient, you are hereby
formally notified that any use, copying or distribution of this e-mail,
in whole or in part, is strictly prohibited. Please notify the sender by
return e-mail and delete this e-mail from your system. Unless explicitly
and conspicuously designated as "E-Contract Intended", this e-mail does
not constitute a contract offer, a contract amendment, or an acceptance
of a contract offer. This e-mail does not constitute a consent to the
use of sender's contact information for direct marketing purposes or for
transfers of data to third parties.
Francais Deutsch Italiano  Espanol  Portugues  Japanese  Chinese  Korean
           http://www.DuPont.com/corp/email_disclaimer.html
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org