Bruce Atherton <bruce@callenish.com> writes:
> At 09:39 AM 12/12/2001 -0500, Greg Hudson wrote:
> >This might be subject to interpretation, but my reading is that there is
> >some kind of Subversion-wide global default line-ending style, which can
> >be overridden by a property, but we apply the global default style to
> >the initial commit if the property is not set.
>
> I hope that is not what was meant, since it mucks with the data much
> more than would be necessary otherwise. But I guess we'll have to wait
> for clarification on that.
That is what was meant; see my latest mail supporting greg's
proposal. I think it makes things much clearer.
> > Presumably there would be some boilerplate as part of the
> >vector graphic program's binary format (just like svndiff has a little
> >ID string at the front). Moreover, I didn't say there were no line
> >endings in the file, just that there was nothing resembling *a line
> >ending which needed translation*. Perhaps the file happens to contain
> >bare LFs but no CRs or CRLFs which would need translation to LFs.
>
> Perfect. So when you checkout the file on Windows, the LF is changed
> to CRLF and you have a corrupt file. The corruption might correct
> itself with Ben's method (a faint hope) but it will not with your
> method.
This has nothing to do with any EOL translation scheme. The user has
the responsiblity to make sure that svn thinks a file is binary. svn
tells you what it thinks the file is when you schedule it for
addition; the user can tweak this via a property. Or the user can
deliberately shut off EOL translation regardless of text-vs-binariness.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:52 2006