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

Re: Enforcing Code Style

From: Tom Browder <tom.browder_at_gmail.com>
Date: Fri, 22 Aug 2008 10:01:44 -0500

On 8/22/08, John Peacock <john.peacock_at_havurah-software.org> wrote:
> Tom Browder wrote:
> > That sounds like a good idea. Am I correct that the script would have
> 1) "blame" relies on which revision changed which line for its display
> (which has nothing to do with whether the commit was substantial or just
> whitespace);
> > Couldn't the script inject a comment somehow?
> Comment what? You obvious would note in the commit for the mass reformat
> that this was done, but you will have "lost" the immediately accessible
> line-oriented history of that file (see below).
> > > you won't be able to tell who added a feature. If this is acceptable,
> Because the first time someone reformats a file, all of those changed lines
> are now attributed to that user, rather than whoever added the lines in the
> first place. Now, it is possible to use blame with a specific revision
> number to go back before the reformat, but it is not nearly as useful.

Thanks, John. Now I understand the white space and formatting issues
better. I haven't used the blame feature because I've not been in a
heavy multi-developer situation locally before.

I'll do some more investigating and revisit this later.


To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-08-22 17:02:09 CEST

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.