@pnkfelix @Wesley Wiser @nikomatsakis Let me know how you want to categorise changes and I’ll factor them out into separate commits.
@Alexander Regueiro Just skimming through the first couple files in your PR, I'd like to see individual commits for each of these:
.to one space
true ifchanges (probably better to leave this out given the controversy)
Any changes to code should definitely go in their own commits.
@Wesley Wiser sounds reasonable. I'm going to implement the URL to issue number changes, since that represents the existing consensus in the codebase, but we can all debate later. Re
true if, I'll normalise to that (even if I don't like it)
@Alexander Regueiro The other thing that might help you get this done quicker is to split up the changes by module or whatever. ljedrz has taken this approach and it seems to have worked well for them: https://github.com/rust-lang/rust/pulls?utf8=%E2%9C%93&q=is%3Apr+author%3Aljedrz+cleanup
People will be faster to review and approve smaller PRs than large ones
@Wesley Wiser okay, sounds fair, ta
(I broke out a topic for this)
(for the record, I think I'd prefer normalising issue numbers to URLs rather than vice versa, as they're more convenient to access)