Timeline for Reformatting and version control
Current License: CC BY-SA 3.0
19 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 25, 2022 at 0:00 | history | tweeted | twitter.com/StackSoftEng/status/1485764415270100996 | ||
| Jan 22, 2022 at 22:37 | answer | added | Thorbjørn Ravn Andersen | timeline score: 1 | |
| Apr 13, 2018 at 2:44 | comment | added | Marnen Laibow-Koser | And I agree with others: don't rewrite your history for the sake of formatting. That defeats the purpose of having a history. | |
| Apr 13, 2018 at 2:43 | comment | added | Marnen Laibow-Koser | "And consistency is more important than minor improvements." Nope. I hate it when a project tries to enforce consistency at the expense of readability. I don't care if code is formatted exactly the same across the project as long as it's all readable and of good quality. | |
| Dec 22, 2013 at 20:59 | comment | added | JensG | In some other languages nobody cares about formatting the code, because the virtually only one accepted standard is enforced by the environment - golang.org/doc/effective_go.html#formatting | |
| Dec 13, 2012 at 11:55 | vote | accept | l0b0 | ||
| Jun 29, 2012 at 21:11 | comment | added | David Cowden | Reformats are code changes and should be committed as such. | |
| Jun 29, 2012 at 20:47 | answer | added | Caleb | timeline score: 4 | |
| Jun 29, 2012 at 15:58 | comment | added | Joris Timmermans | In some languages (I'm looking at YOU, Python) reformatting can change the logical functioning of the code. You'd have to be able to parse all languages stored in your VCS to track and ignore reformats safely. | |
| Jun 28, 2012 at 21:20 | answer | added | mjfgates | timeline score: 10 | |
| Jun 28, 2012 at 21:06 | comment | added | Andrew T Finnell | On a unrelated topic, it sounds like you were suggesting to rewrite Git history by reformatting all the code. Don't give people idea, rewriting Git history is bad for 99.9% of the cases. Reformatting is not the .1% edge case. | |
| Jun 28, 2012 at 20:37 | answer | added | harald | timeline score: 30 | |
| Jun 28, 2012 at 20:10 | comment | added | l0b0 | @Simon: I'd like a set of tools which allow me to refactor without having to worry about such things. Maybe something like a parallel history (higher level than a branch) recording the new progression. | |
| Jun 28, 2012 at 20:08 | history | edited | l0b0 | CC BY-SA 3.0 |
added 550 characters in body
|
| Jun 28, 2012 at 18:05 | comment | added | rlperez | I like to comment commits that I do this with tagged with "Reformat. No functional change" | |
| Jun 28, 2012 at 18:03 | answer | added | janos | timeline score: 14 | |
| Jun 28, 2012 at 16:56 | answer | added | JBRWilkinson | timeline score: 1 | |
| Jun 28, 2012 at 15:35 | comment | added | Simon Bergot | Why would you want to rewrite history? It defeats the purpose of version control. You want to make sure that the application you shipped 3 month ago matches the revision xxxxxx without the slightest doubt. Even trivial reformatting is unacceptable. | |
| Jun 28, 2012 at 15:30 | history | asked | l0b0 | CC BY-SA 3.0 |