Roman Neuhauser <neuhauser@mobil.cz> writes:
> I don't think the issue is notepad displaying LF files as a single
> line with some strange hollow squares instead of newlines. But no
> EOL conversion could bite you in quite a few situations... IIRC
> UltraEdit can be set up to display LF files properly, and convert
> them to CRLF when you write them out. Check out, modify a single
> line, and commit. Oops, the diff is somewhat longer than
> expected...
You do recall correctly (I used UltraEdit all the time). However,
that's a problem with the how the UltraEdit tool was handled on the
source code, not how Subversion handled the versioning/retrieval of
such.
> > * Mike Pilato argues (convincingly, IMHO) that newline conversion
> > is way outside the scope of a version control system anyway, that
> > it's just a weird bit of creeping featurism that doesn't even
> > provide something terribly useful anymore, and has the potential
> > to damage data (since it's a departure from faithfully versioning
> > whatever people checked in).
>
> Well, this is a matter of taste. I could agree that EOL conversion
> is beyond the scope of a RCS, but then I could also argue that so is
> the "commit email" feature, for example. It has nothing to do with
> revision control after all.
You're absolutely correct. And thankfully, Subversion has no support
for commit emails, either. We do, however, have tools (external to
Subversion, mind you) and a good API that can assemble a commit mail
and dispatch it. Likewise, you could have a tool (again, external to
Subversion) that converts your line-endings back and forth for you.
---------------------------------------------------------------------
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