[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: eol style differences

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2003-03-11 23:34:17 CET

"Sander Striker" <striker@apache.org> writes:

> > Of course, it sounds like now, you can successfully "svn diff",
> > but it won't tell you where your problem is.
>
> Right, so we need to do the translations the other way around and
> compare in working copy style. Anyone care to make that change?
> Or file an issue?

Using working copy style might be better most of the time (I'm not
really convinced but I'll just assume it is for now), but it's not
clear to me that it is always better. Two problems come to mind.
First, suppose one is comparing two different revisions, using '-rX'
or '-rX:Y', then there will be two svn:eol-styles and they may not be
the same. Does each revision of the file get translated according to
it's own svn:eol-style, or does one svn:eol-style get used for both?

The second problem is more to do with how svn:eol-style works in
general. It is possible to have a repository format file with CRLF
line-endings and svn:eol-style set to native. On Windows a repository
format comparison should show every line changed, a working copy
comparison should show no change. Which is correct?

Perhaps the solution is that whichever format we choose to use for
diff, a command line flag should be available to cause the other
format to be used.

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Mar 11 23:35:05 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.