"Perry E. Metzger" <perry@piermont.com> writes:
> What I am guessing is happening is this, though I may be totally
> wrong. I'm guessing that subversion imports the files in as "binary",
> and treats eol-style as some sort of postprocessing it does during
> checkout which has no impact on diffs in the server done for
> deltification and other purposes. When I tried to do the svn cp +
> svn commit locally, it noted the fact that every line was different
> between the two versions and doubled the size of the test repository.
>
> My guess is that if eol-style is set to "native", files should be
> imported in some sort of canonicalized line ending style to prevent
> this sort of thing from happening, though it isn't clear what to do if
> you forget that when you import and change the eol-style
> afterward. Anyway, it is highly unexpected behavior, and might cause
> trouble with merges and other similar behavior later on -- it should
> be fixed somehow. I can imagine merges and commits between different
> platforms causing the repository copy to have all sorts of weird line
> endings in different parts of the files if that's the case.
Sounds like
http://subversion.tigris.org/issues/show_bug.cgi?id=1756
maybe?
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Feb 24 23:45:07 2004