[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: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2003-03-11 21:23:09 CET

(I wish there were a mail archive of this list which kept message IDs,
so I could generate proper responses after accidentally deleting the
mail I want to respond to.)

Branko wrote:
> Whichever code it is, it's doing the wrong thing. The text base
> should be converted to WC style, not the other way around, otherwise
> you won't notice newline-only changes.

> Oh, duh -- that would make keyword expansions cause problems for us
> again. What a bore.

This just means we have to parameterize the keyword expansion code so
that we can say "expand this text base with the same substitutions as
we used on the working copy."

> Hmm, maybe the conversion from WC style to text-base style should
> notice if the WC file line endings aren't consistent with what's
> declared in svn:eol-style?

I think it used to, but we turned that check off for everything but
"svn commit" after someone complained that it was difficult to recover
from having inconsistent newlines. You couldn't even "svn revert" at
that time, which was really bad, but you also couldn't "svn diff" to
find out where your problem was. Of course, it sounds like now, you
can successfully "svn diff", but it won't tell you where your problem
is.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Mar 11 21:23:54 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.