[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: RE: Post Commit Code Formatting

From: Neulinger, Nathan <nneul_at_umr.edu>
Date: 2005-06-22 23:02:12 CEST

> I'm not convinced. There really is no reason that code formatting
> shouldn't be integrated into a repository. It still seems to
> me that it
> would be very convenient to check-out a piece of code, have
> it displayed
> in a format it to my liking, modify it, then check it back it without
> thinking of the formatting. If there is a conflict, the diff will be
> displayed post-format, which will factor out all insignificant
> differences and show only logic differences. This is simply an
> enhancement to a tool, allowing developers to work in a style
> they feel
> comfortable in while still maintaining a consistent easily
> diff'ed style
> in the repository. Formatting factors out insignificant changes, so
> revision 1.1 is truly different than revision 1.2.

That's not entirely true... If your edit causes a missed
paren/brace/etc, the reformat will likely be very screwed up looking,
and the little details of what you actually changed will be lost in the
big changes due to the huge reformat/reindentation.

-- Nathan

Nathan Neulinger EMail: nneul@umr.edu
University of Missouri - Rolla Phone: (573) 341-6679
UMR Information Technology Fax: (573) 341-4216

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jun 22 23:17:14 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.