I'd like to use Eclipse's formatter to fix some poorly styled code, but there's a huge downside to killing all the metadata in the repository about who is responsible for what. Any thoughts on ways to get around this? Perhaps it is just completely impossible...
+1
A:
The history is still there, you'll just have to look at a blame prior to the cleanup revision.
This is one good reason to have a style standard. Indentation changes can cause a lot of merge conflicts, etc. "Poorly styled" to one is well written to another.
jthompson
2009-03-27 04:39:14
sadly, there's a large base of poorly styled code to start. I guess one pain point is that eclipse annotations only show the most recent change. And people use them a fair amount.
Jacob
2009-03-27 04:53:20
+3
A:
You can tell blame to ignore whitespace changes:
svn blame -x -w file/path
Of course that only works if your style fix doesn't change more than whitespaces.
Stefan
2009-03-27 07:08:48
A:
When reformatting code, I usually only fix the indentation. There are just too many cases where the automatic formatter ruins a carefully hand-formatted section.
Aaron Digulla
2009-03-27 09:38:09