On Friday 02 February 2007 14:46, Hilco Wijbenga wrote:
> > > TEXT\r\n
> > > or
> > > TEXT\r
> > > \n
> >
> > ^^^^^ I see you are inherent DOS user, assuming "\r\n" means
> > line-end
>
> No, I'm on Linux. I'm not assuming anything ... I'm trying to point
> out that it is (in general) impossible to determine how many lines
> (i.e. EOLs) a "text" file contains if mixed EOL indicators are
> being used.
Don't underestimate yourself... it would be impossible for you to not
assume one thing or another. I know it's not your point, but you said
"Does that mean [...]", then instead of specifying which sequence you
thought was [EOL], you wanted us to assume that \r\n was a single
[EOL].
Great (sarcastically), you would also be saying that subversion is
already completely wrong. Note that even if the entire file uses
\r\n, it would be impossible to determine that this is not meant to
be double-spaced: \r from the original single-spacing, then strange
editor adds \n at each line in attempt to double-space. Certainly
that possibility is not realistic to worry about, so svn assumes no
problem. Otherwise we need to immediately rip out the whole weak
solution that svn was attempting and bar productivity already in
progress, when instead we could have took a deep breath and added the
trivial change to make us all happy.
Remember that I am not proposing to change svn to do something
different than it does without user specifically asking (perhaps via
auto-props). I hope you realize that there are already many ways that
an import goes wrong already. You will not escape that by risk by
avoiding this simple feature request. It would add more to solutions
than to possible things going wrong.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 2 23:11:45 2007