Timeline for Reformatting and version control
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 23, 2021 at 6:50 | comment | added | Thorbjørn Ravn Andersen | You might also choose a good point in time to do this, combined with automatic reformat on save in your IDE. | |
| Feb 5, 2016 at 10:01 | comment | added | harald | In programming, nothing is as simple as it sounds :) | |
| Feb 5, 2016 at 6:42 | comment | added | Johntron | Yeah, lots of problems :P I just want to caution new developers that it's not a simple as it sounds. Bulk-reformatting tools are risky (especially if you build it yourself with regex - at least use AST), and if you care about code review and bug tracking, it can really mess with your process. Personally, I write my code to be consistent with the style of each file, though I don't mind reviewing code when a few functions are reformatted. Many developers get hung up on code style and neglect the bigger issues like architecture, process, tooling, etc. | |
| Jan 23, 2016 at 17:31 | comment | added | harald | Sounds like the team in question has bigger problems than code formatting. But yeah, I don't recommend doing this unless you thing you have to. If you want to do reformatting changes, I'd still say better do them as separate commits than intermixed with functional changes. | |
| Jan 18, 2016 at 20:41 | comment | added | Johntron | I've seen projects derailed for weeks because one of the developers thought this was a good idea. If you're going to do this, understand the risks beforehand, and decide exactly how far you're going to go with the formatting. I think mjfgates has the right answer. | |
| Dec 13, 2012 at 11:55 | vote | accept | l0b0 | ||
| Jun 28, 2012 at 20:37 | history | answered | harald | CC BY-SA 3.0 |