Forwarding my response back to the list...
---------- Forwarded message ----------
From: Erik Huelsmann <ehuels_at_gmail.com>
Date: Mon, Mar 12, 2012 at 4:14 PM
Subject: Re: Compressed Pristines
To: Johan Corveleyn <jcorvel_at_gmail.com>
Hi Johan,
> Has nothing to do with the property. The pristine matches the repository,
> > byte for byte. The file installed in the working copy is affected by the
> > property; not the pristine.
>
> Yes, the pristine matches the repository. But what I mean is:
>
> (on Windows):
> $ create file-with-crlf.txt
> $ svn add file-with-crlf.txt
> $ svn ps svn:eol-style native file-with-crlf.txt
> $ svn commit -mm file-with-crlf.txt
>
> -> pristine file is LF-terminated (as is the file in the repos, as you
> point out).
>
This is correct: line endings get normalized to LF when svn:eol-style
'native' is applied.
> $ create file-with-crlf.txt
> $ svn add file-with-crlf.txt
> $ svn commit -mm file-with-crlf.txt
>
> -> pristine file CRLF-terminated.
>
This is correct: file doesn't have any transformation applied: we preserve
the input file.
> $ create file-with-crlf.txt
> $ svn add file-with-crlf.txt
> $ svn ps svn:eol-style CRLF file-with-crlf.txt
> $ svn commit -mm file-with-crlf.txt
>
> -> pristine file CRLF-terminated.
>
This is correct: it's the normal form for files with CRLF applied (before
you ask: files with CR line ending normalization get transformed to CR
only).
> $ create file-with-crlf.txt
> $ svn add file-with-crlf.txt
> $ svn ps svn:eol-style LF file-with-crlf.txt
> $ svn commit -mm file-with-crlf.txt
>
> -> pristine file is LF-terminated (as is the working-copy file).
Exactly. So what you found is that for any eol style other than native, we
use exactly that style. For native, we use LF.
HTH,
Erik.
Received on 2012-03-12 16:15:42 CET