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

Re: Coding system for output of "svn cat"

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Mon, 27 Aug 2012 14:41:27 +0100

Andre Colomb wrote on Mon, Aug 27, 2012 at 14:26:17 +0200:
> Hi list!
>
> I couldn't find any information about this in the Subversion book or the
> built-in documentation.
>
> What is the EOL encoding of text files spit out by the svn cat command?
> Does it depend on the svn:eol-style property?
>
> I'm trying to improve the contributed psvn.el mode and need to figure
> out how to get rid of extra ^M characters at the end of every line when
> checking out an older revision (which uses svn cat internally) and
> comparing it with the working copy.
>

When svn:eol-style=native, the file is stored in the repository with LF
line feeds. (See "repository normal form" --- LF line feeds and
contracted $Keywords$.)

I assume you have cases where svn:eol-style was set on a file partway
through its history. Due to the above implementation detail, I wonder
if you'll find that the behaviour differs for setting
svn:eol-style=native on a file that was CRLF beforehand compared to
setting it on a file that was LF beforehand...

I suspect svn's diff algorithm will _not_ normalise the EOL style on
revisions that didn't have the property set, but perhaps that's exactly
what you'll be doing.

> Thanks in advance and kind regards,
> André
> --
> Greetings...
> From: Andre Colomb <acolomb_at_schickhardt.org>
>
Received on 2012-08-27 15:42:02 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.