Timeline for Reformatting and version control
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 8, 2019 at 17:28 | comment | added | Druska | I've done both of these approaches. The first approach is very obtrusive because there will be a ton of changes every time a new file is committed for the first time. The second approach is better for the team, like ripping off a bandaid quick. | |
| Jun 28, 2012 at 20:25 | comment | added | user1249 | If the IDE's support it then there is also 3) have the IDE autoformat at save. Then just use the same settings everywhere - this is easiest if you use the default with the IDE. | |
| Jun 28, 2012 at 20:12 | comment | added | l0b0 | @Sign: Exactly my point - When the commit hook changes, your history could deteriorate into something almost useless. Formatting which doesn't change functionality shouldn't be a commit, it should be transplanted throughout the code history. | |
| Jun 28, 2012 at 18:23 | comment | added | Sign | Wouldn't option one when turned on ripple across the majority of the code base quickly resulting in the same big bang of having each file change? | |
| Jun 28, 2012 at 16:56 | history | answered | JBRWilkinson | CC BY-SA 3.0 |