Graf Zahl wrote:I guess it's off because it's a destructive option by its very nature
What do you mean destructive? Having SVN handle the line endings automatically leads to fewer whitespace-only commits, wouldn't that be a good thing?
I suppose it would make a digest hash on the checked-out source fail, but I don't see any reason anyone would make the hash of a specific SVN source tree matter. Maybe for tags I guess, if for some reason the line endings are somehow critical to the build process. (o.O)
Graf Zahl wrote:I know tools that get hopelessly confused if stuff can get changed that way.
How could the tools get confused? eol-style:native makes the line endings consistent for the system you're using specifically to
avoid getting your tools confused. I would be curious to see an example of where using the system's native line endings causes a problem.
Not even going to touch the bait on that second line.

[quote="Graf Zahl"]I guess it's off because it's a destructive option by its very nature[/quote]
What do you mean destructive? Having SVN handle the line endings automatically leads to fewer whitespace-only commits, wouldn't that be a good thing?
I suppose it would make a digest hash on the checked-out source fail, but I don't see any reason anyone would make the hash of a specific SVN source tree matter. Maybe for tags I guess, if for some reason the line endings are somehow critical to the build process. (o.O)
[quote="Graf Zahl"]I know tools that get hopelessly confused if stuff can get changed that way.[/quote]
How could the tools get confused? eol-style:native makes the line endings consistent for the system you're using specifically to [i]avoid[/i] getting your tools confused. I would be curious to see an example of where using the system's native line endings causes a problem.
Not even going to touch the bait on that second line. :lol: