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

Re: Mixed workspaces in windows and *nix

From: Andrey Repin <anrdaemon_at_freemail.ru>
Date: Wed, 29 Apr 2009 23:52:35 +0400

Greetings, Jose Garcia Juanino!

>> > it is posible to create an subversion workspace in solaris, to
>> > transport
>> > to a windows SO, and working with it here? For example:
>> >
>> > $ uname
>> > $ SunOs
>> > $ svn co http://svnrepos myWorkSpace.svn
>> > $ zip -r myWorkSpace.svn.zip myWorkSpace.svn
>> >
>> > $ ( transport myWorkSpace.svn.zip to a windows machine and unzip, and
>> > attach myWorkSpace.svn to a Tortoise SVN client).
>>
>> It can be done, but if you have set svn:eol-style to native on any
>> files, they will be native to whatever platform you checked out on,
>> and will be wrong if you transport the working copy to an OS that
>> uses different line endings.

> Thanks a lot for your reply. The svn:eol-style issue is not a problem
> for me. I am only concerned with the internal structure of .svn
> directories, as I am not sure if they are platform independent. It
> the answer is "yes", workspaces are platform independent, except for
> the svn:eol-style issue.

Workspaces itself platform-independent without an exception.
eol-style will be an issue only when you start committing your files to
repository.
If, say, you CO your files with EOL=LF, and your editor change them all to
CRLF then, even if you didn't changed any meaningful line in file, the file
itself will be considered modified just in case of these added CR's.

--
WBR,
 Andrey Repin (anrdaemon_at_freemail.ru) 29.04.2009, <23:50>
Sorry for my terrible english...
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1984377
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-04-29 21:56:33 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.