Re: Mixed Unix-Windows development

Greetings, Alexey Ivanov!

> As I've read in the SVNbook (red-bean)
> http://svnbook.red-bean.com/en/1.5/svn.advanced.props.file-portability.html#svn.advanced.props.special.eol-style
> - I can tune Subversion so, that when our code is committed under Windows -
> CR-LF will be translated to LF, so Unix developers will be happy.

> I can select the commit mode: to keep CR-LF in the code forever, to keep LF
> forever or to use "native" line endings.

No, seriously, you got it absolutely wrong.
It does not commit what, it check out what.
If you set svn:eol-style to native your checkouts will have line-endings
native to the system you've checked it out, but what is stored in SVN is a
whole different question, not related to your issue.

> It was very pity for me, that all this tuning works only for commit operation,
> not for checkout or update.

You must tell your developers to add files with proper properties (in case -
svn:eol-style).
Then it will work as you want.

> In other words: if Unix developer commits some code - Windows developer
> cannot receive it with Windows line endings even if this file has svn:eol-style=native
> property.

This not sounds right. Some logs to confirm your case?

> This behavior contradicts to the description of "native" svn:eol-style property in the SVNbook,
> but it was that I've seen in my testing.

> Is there any solution?

First, I think it'd be good to provide logs. A testcase may be.
Second... just to say that... svn+ssh is not very good idea, really. Requires
too much care to manage. My personal opinion.

--
WBR,
 Andrey Repin (anrdaemon_at_freemail.ru) 17.05.2009, <7:19>
Sorry for my terrible english...
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2287381
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].