On Jan 18, 2013 10:17 AM, "Jan Stolarek"
I don't think it's worth the bother either: conflicts are a pain and slow down development, whereas tabs don't. (...) there certainly are a few active branches with large-scale changes. That's another good point.
I looked through the git history and it seems there are actually few tabbed files that weren't touched for the last 6 months. It follows that tabbed files that people work on are not being actually detabbed by them, unless the policy is to detab only the parts that are modified, not the whole file.
I won't do this massive detabbing of the whole source since it indeed could cause more problems than profits, but my opinion is that at some point detabbing should be just done or otherwise those -fno-warn pragmas and tabs will stay in the source code forever. Perhaps it would be a good idea to detab a bunch of files every month?
Well if this is true, then I think you could solve this simply by looking for this in a git commit hook or some other hook. http://stackoverflow.com/questions/3985463/prevent-pushes-to-git-containing-... https://github.com/mrc/git-hook-library Alexander