Comment #7 on issue 3499 by miguel.coba: FixUnderscores (package & instructions) out of date
http://code.google.com/p/pharo/issues/detail?id=3499
I also think that the FixUnderscores are a bad solution to the problem. The point of having the source code versioned is to track *every* change to it. that includes, accents, spaces, newlines, and of course, source code. I don't know why the underscores should be treated differently. It *is* a change in the code. And it is good to have the source code management system to trackit. Even if no other change more semantic was made. So I vote also for the rules for the refactoring browser and the lint rules to search for underscores in the core image.
