On Wed, Jul 29, 2009 at 2:50 PM, Haggerty, Joshua
<Joshua.Haggerty_at_kci1.com>wrote:
> Our developers use subversion and edit source code on windows- our
> deployers checkout and scripts run on unix- and so we run into the dreaded
> ^M problem frequently- typical paradigm.
>
>
>
> I have read about setting the property svn:eol-style and autoprops, but
> these are all client side and so I have to communicate the process with 50
> developers and depend that they do it right. So instead- we wrote a post
> commit hook script that looks at the file extension then sets eol-style to
> native (if it .sh for instance) on that revision (had to do at revision
> because we needed to do it by URL not working copy as we are on the
> server). Works great- basically sets that property on every revision
> committed- but the eof:style doesn’t appear to do anything on revisions. We
> still have ^M’s when we set on the revision instead of no ^M’s when we set
> on the working copy file.
>
>
>
> Any explanations or ideas on alternatives are appreciated.
>
svn:eol-style is not a revision property. It is a file property. So you can
not set it per revision. You have to set if for the file. That is why you
are seeing it to work when you set it on the file in the working copy.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2376754
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-07-30 00:16:49 CEST