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

Re: [Issue 524] Changed - line-ending conversion and keyword expansion

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2001-11-08 20:45:37 CET

Branko Čibej <brane@xbc.nu> writes:
> I guessed it would be something like that. However, that doesn't
> change my position: the native newline separator is a property of the
> whole repository. I really don't see why one should be able to change
> this per file, or per directory.

I don't understand why the repository has to have a "native newline
separator" at all.

If newline conversion is done entirely on the client side, then it
doesn't matter how the repository stores a file -- it can just store
it however it was checked in. Doesn't matter if that's LF, CRLF, or
LFCR. The *file* itself (or its parent directory, whatever) should
indicate what kind of file it is.

Here's how the client deals with this:

   - If the file (or parent dir, whatever) has no properties
     indicating that any particular sort of newline conversion should
     happen, then it just gets checked out as-is.

   - If props indicate that platform-specific conversion should be
     done, and that this file is a "text" file of type "xxx" (where
     "xxx" indicates its newline style), then all xxx newlines in the
     file get converted to client-local newlines, and the reverse
     conversion happens on the way back to the server.

Why does the repository have to know anything about newline styles?


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:48 2006

This is an archived mail posted to the Subversion Dev mailing list.