Reputation: 28818
I often have lots of whitespace-only changes (spaces turning to tabs or vice versa etc.) and I generally don't care about these changes. I know that whitespace could be important (i.e. some whitespace changes can be breaking), but it would be very useful if there was a way to tell when looking at huge lists of files which ones contain whitespace changes only.
Please I am not looking for the "you should never have that many files to check in" kind of response, I'm aware of that already - this is just the situation and I'd like some advice!
Thanks.
Upvotes: 4
Views: 1856
Reputation: 88
I know this is an old post but I just ran into a similar situation. What I did was use TortoiseSVN's "Create Patch" feature and selected "Ignore whitespace changes" in the options window. Then I just reverted the working directory to the trunk, applied the patch, and committed.
Upvotes: 4
Reputation: 11217
What about pre-commit hook changing tabs to spaces? :) That way will the checkouted files always with spaces ;)
Upvotes: 0
Reputation: 8972
I don't think you can. You should probably relegate them to different commits. I.E. have one commit that contains all the whitespace/formatting changes with a comment to that effect then another that contains the actual code/logic changes.
Upvotes: 0