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

Re: --native-eol setting not applied to externals?

From: Mark Hanson <mbh000_at_gmail.com>
Date: Thu, 22 Jul 2010 07:25:58 -0700

On Wed, Jul 21, 2010 at 11:03 PM, Daniel Shahaf <d.s_at_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
Received on 2010-07-22 16:27:27 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.