Mark Hanson wrote on Wed, Jul 21, 2010 at 08:37:25 -0700: > I have a set of source code containing a some svn:externals references to > other repositories. In each group of code, there are text files marked with > the svn:eol-style property, value: native. > > If I export all the source without using --native-eol on Windows or UNIX, the > text files are all in the expected format (CRLF or LF, respectively). > > If I export all the source on Windows, using the --native-eol LF option, the > text files in the non-external area are correctly in UNIX LF format. The > text files in the external areas are in the native Windows CRLF format. > Apparently the --native-eol setting is not applied to the source in the > external areas. > > If I export all the source on UNIX, using the --native-eol CRLF option, the > same problem occurs in reverse. The non-external text files are correctly in > Windows CRLF format, and the external text files are in the native LF format. > > I think the expected behavior should be to have all the source (main and > external) exported in the format specified with the --native-eol option. > > As a workaround, we are currently exporting the externals separately, with > the appropriate --native-eol option, after exporting the main source with the > --ignore-externals option. This works as expected. > > The versions of client and servers are all >= 1.6.5. > > 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. > Thanks, Mark >
