Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

9
  • 25
    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. Commented Jun 28, 2012 at 15:35
  • 5
    I like to comment commits that I do this with tagged with "Reformat. No functional change" Commented Jun 28, 2012 at 18:05
  • 3
    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. Commented Jun 28, 2012 at 21:06
  • 4
    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. Commented Jun 29, 2012 at 15:58
  • 3
    Reformats are code changes and should be committed as such. Commented Jun 29, 2012 at 21:11