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

Re: svn blame and code reformatting (was: [VOTE] space before paren policy)

From: <kfogel_at_collab.net>
Date: 2006-01-30 15:31:58 CET

Vincent Lefevre <vincent+svn@vinc17.org> writes:
> On 2006-01-29 08:37:12 -0600, kfogel@collab.net wrote:
> > Folks, remember that reformatting old code will affect 'svn blame'
> > information, and may make it harder to apply some currently
> > outstanding patches. I'm not saying these issues should be decisive,
> > just wanted to make sure everyone was aware of them before voting.
>
> Concerning 'svn blame', is this a good reason? I've noticed that
> there is the same problem when the indentation must be changed
> (e.g. because a 'if' is added...). IMHO, 'svn blame' should have
> an option to be space-insensitive (possibly depending of where
> the space occurs -- and this could depend on the svn:mime-type
> value).

I gave this some thought once, and came to the tentative conclusion
that it's not trivial to implement.

Actually, what I was thinking of was an 'svn:blame-transparent'
revision property, that would cause that revision to be "transparent"
to 'svn blame'. This way one could commit formatting fixes in their
own revision, and have that revision not affect the blame information.
It was only when I started thinking about what this would actually
mean, in concrete terms, that it started to get slippery... But if you
(or someone) can figure out a way to do it, +1 :-).

-Karl

-- 
www.collab.net  <>  CollabNet  |  Distributed Development On Demand
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jan 30 17:12:17 2006

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