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

Re: Faulty line-end handling in "svnadmin load"?

From: Karl Fogel <kfogel_at_red-bean.com>
Date: 2007-08-20 23:35:14 CEST

Michael Haggerty <mhagger@alum.mit.edu> writes:
> On the cvs2svn mailing list, somebody wrote the message quoted below.
> He claims, basically, that if a file that has svn:eol-style=CRLF is
> written to a dump file with different line-end convention, then "svn
> diff" gets confused.

What's scary about this question is that it (maybe?) implies that an
SVN dumpfile can have different line-end conventions :-).

http://svn.collab.net/repos/svn/trunk/notes/dump-load-format.txt
strongly implies (without quite stating explicitly) that LF is the
line-ending format for a dumpfile, in the sense that the metadata
sections should have lines ending with LF. Of course, the format is
really binary, since a given file's contents within a dumpfile might
contain anything at all.

Regarding file contents:

As Mike Pilato pointed out, text files with svn:eol-style set to
'native' should be repository normal form (LF); files with
svn:eol-style set to a specific line-ending format should be stored in
that format; and files without the property are just binary blobs, for
the purposes of line-endings.

So I don't know how this person's CRLF file got written to the
dumpfile with a different line-end convention, but that's where the
badness stared. If Subversion did that, then Subversion has a bug.

-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Aug 20 23:32:57 2007

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