On Wed, Jul 21, 2010 at 11:03 PM, Daniel Shahaf <d...@daniel.shahaf.name> wrote: > Mark Hanson wrote on Wed, Jul 21, 2010 at 08:37:25 -0700: >> Can anyone confirm? > > No. Using July 18 trunk, both with file externals and directory externals, an > exported file with svn:eol-style=native has the --native-eol end-of-lines in > the > export. > > I used the 'svn export --native-eol=foo WC WC' syntax.
Here's a script that reproduces the problem on UNIX with 1.6.12. The output I get is: + file exp/foo.txt exp/repo2/foo.txt exp/foo.txt: ASCII text, with CRLF line terminators exp/repo2/foo.txt: ASCII text Does this reproduce with the trunk? Was this a known problem that has been fixed? #!/bin/sh -x mkdir scratch; cd scratch svnadmin create /tmp/repo1 svnadmin create /tmp/repo2 svn co file:///tmp/repo1 repo1 svn co file:///tmp/repo2 repo2 (echo "this is a"; echo "text file") > foo.txt cp foo.txt repo1 cp foo.txt repo2 svn add repo1/foo.txt svn add repo2/foo.txt svn ps svn:eol-style native repo1/foo.txt svn ps svn:eol-style native repo2/foo.txt svn ps svn:externals 'file:///tmp/repo2 repo2' repo1 svn commit -m 'add text file and svn:externals' repo1 svn commit -m 'add text file' repo2 svn export --native-eol CRLF file:///tmp/repo1 exp file exp/foo.txt exp/repo2/foo.txt