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

Re: Merge bug(let)

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2003-02-26 14:12:30 CET

Philip Martin <philip@codematters.co.uk> writes:

> > > Note that the three files could each have svn:eol-style set to a
> > > different value.
> >
> > Hmpf, yes, that would be a problem.
> >
> > > Would you use the the setting appropriate for each
> > > file or would you pick one, the working copy most probably, and use
> > > that for all the files?
> >
> > And that sounds like a viable solution ;)
>
> Given my analysis above, I think the setting for the new merge source
> might be better. Tricky stuff this eol-conversion...

Eeek! That's not right! Suppose we merge an old change where neither
source has svn:eol-style into a working copy with svn:eol-style set to
native. In that case we probably want it all done using native.

How about this: if the merge changes the svn:eol-style then we use the
new style (that of the new merge source) for all the files. If the
merge doesn't change the svn:eol-style then we use the working copy
svn:eol-style for all files.

<Whisper>
Or how about we abandon eol-conversion as a bad idea?
</Whisper>

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Feb 26 14:13:11 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.