Re: svn blame and code reformatting

Sander Striker wrote:
> Even in this project, where people are very strict about that;
> consider the example of adding an if {} block which requires
> reindenting. So I would be -1 on adding a hack like
> svn:blame-transparent as a general feature.

Karl seems to be suggesting an ephemeral property (one that applied to
that revision only), so it could be used to say "this *specific* rev
shouldn't be used for blame purposes." If you had a mixed commit (code
and whitespace) then you simply wouldn't set the property for that
revision. The complication is that svn:blame-transparent would have to
set up to be multivalued, since there might be an instance where more
than one revision might need to be ignored.

Unfortunately, I think the most appropriate fix is to implement diff's
--ignore-whitespace feature (which would be useful in general for other
reasons) then allow blame to respect that when generating the blame
report...

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org