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

Re: Migrating repository from Windows to UNIX and eol-style

From: Andy Levy <andy.levy_at_gmail.com>
Date: 2006-06-29 00:50:37 CEST

On 6/28/06, Joe <dev@freedomcircle.net> wrote:
> Ryan Schmidt wrote:
> > The svn:eol-style property and svnadmin dump have nothing to do with one
> > another. It sounds like you've just been checking in files with DOS
> > linefeeds, and without any svn:eol-style property. Wouldn't matter what
> > OS the server is running on; it'll just accept and store the bytes you
> > send it. If you send it DOS linefeeds, it'll store those.
> The files were typically created on Windows using gvim so each original
> file had CR-LF end-of-lines. I was under the (perhaps mistaken)
> impression that unless you specified something to the contrary,
> Subversion used native eol-style, which would be CRLF on Windows, but
> would "actually store the file in the repository using normalized LF EOL
> markers regardless of the operating system" (Chapter 7). You seem to
> imply that one *has* to specify the svn:eol-style property initially,
> rather than getting the OS default. Is that correct?

svn:eol-style only affects the eol-style that appears when you do the
checkout. Internally, SVN always uses LF. eol-style is more for
user/developer convenience and ease of merging than anything else.

IOW, if you're moving the *repository* from Windows to UNIX, this
property doesn't mean a thing. If you've been doing all your
checkouts on Windows and are moving your clients to BSD or will have a
mixed environment, then it's a really good idea to apply this

If you want to do a mass conversion, you can, and it'll be only a
property change, there won't be any delta on the file contents
themselves. You can take this opportunity to set up a robust
auto-props section in your Subversion client configuration, and apply
all those properties across your whole WC using
svn_apply_autoprops.pl. To do all your code, however, you'll have to
check out the whole repository. Maybe better just to do trunk and
selected, active branches.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 29 00:51:52 2006

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.