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

"--native-eol" to other commands than "cvs export"?

From: Johan Holmberg <holmberg_at_iar.se>
Date: 2006-10-24 12:38:09 CEST


I wonder if it is possible to "fool" Subversion that the "native eol"
convention is different than what is actually is. I have seen the
--native-eol option to "svn export". But I would have wanted a similar
option for "svn co", and that later subcommands operating on the working
copy would also understand that I had done a "svn co" with the unusual
setting of --native-eol.


I have a project where my working copy resides on a Linux disk. The
files are accessed in two different ways:

1) "Normal users" access the files via Samba from Windows-clients. They
don't even know that the files are administered by Subversion (and this
is intentional).

2) "Admin users" handle the fact that the files are stored in
Subversion. Currently I check out the files with "svn co" from a Windows
client and store them on the Samba share exported by the Linux box. If I
could have done "svn co" (and other subcommands) locally on the Linux
box things would have been many times faster. But switching to do "svn
co" would also imply a change of "native eol", and that doesn't work for
the "normal users".

/Johan Holmberg

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Oct 24 12:38:59 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.