Hi Paul, I'm with you all the way. No one can guarantee that "cleanup" will not modify the intent of the original, especially if the original was sufficiently weird. <g> "indent" will probably not modify C code. It can mess up text strings embedded in it, if they have blank space at the start of the line. In XML, though, indenting can mess it up. All my very best, Rob -- Rob Echlin, B. Eng. 613-266-8311 - Ottawa, ON http://talksoftware.wordpress.com - http://picasaweb.google.com/coderoller On Tuesday, September 23, 2014 2:28 PM, Paul Hays <Paul [ dot ] Hays [ at ] cattail [ dot ] ca> wrote: > > >Commit early, commit often. > >Yes, the manager was right; I'd start a repo with as-is code. When that >rare (but reproducible) defect appears months later, 'git bisect' could >help find the code affected by the typo or brain-fade at the root of the >problem. Ref: http://git-scm.com/book/en/Git-Tools-Debugging-with-Git > >OK, you might think fixing comments couldn't possibly introduce a bug, >but I've seen some strange finger trouble. Hmmm, 'indent' *might* never >break code... but I'm on the border between defensive coding and paranoia! > >-- >Paul Hays <Paul [ dot ] Hays [ at ] cattail [ dot ] ca>, GnuPG id: D611A870 > > >_______________________________________________ >Linux mailing list >Linux [ at ] lists [ dot ] oclug [ dot ] on [ dot ] ca >http://oclug.on.ca/mailman/listinfo/linux > > >