I’ve spoken previously about the travails of having a developer community that uses both Windows and Unix-based machines: merging files edited in both environments. Hopefully those days are over. (At least for the OpenMRS community)

Chase Yarbrough attempted to fix this by adding the svn:eol-style to all of the files in the OpenMRS repository recursively. The problem is that all files that were already committed from both operating systems failed with:

svn: File ‘somefilename.ext’ has inconsistent newlines
svn: Inconsistent line ending style

However, merging continued to be a pain with those files that were skipped over.


I created a short script to recursively loop over all files in the root directory, run dos2unix, and then set the svn:eol-style to CRLF:

Download this script


# This script normalizes the newlines in all files in
# a directory and adds the svn:eol-style property
# Author: Ben Wolfe - 10/2008
# http://blog.eflow.org


# get a flat list of all files under the current directory
f=`ls -RlQ | awk -v PATH=$path '{ \
if ($1 ~ /.*:$/) \
path = substr($1,3,length($1)-4); \
else \
if ($0 ~ /^-/) \
printf("%s%s/%s\n", PATH, path, \
substr($0, match($0,"\".*\"")+1, RLENGTH-2) \
) \

for i in $f
#ignore the build folder contents
if ! echo $i | grep build > /dev/null;
        #check subversion for this property
        x=`svn propget svn:eol-style $i`
        if [ ! -n "$x" ]
                # get the file's extension
                ext=`echo "$i" | awk -F . '{print $NF}'`

                # This is an "if list contains" method for shell scripts
                # check if ext is one of the text based extensions
                case $ext in
                                #echo No svn:eol-style prop: $i . Adding now.
                                dos2unix -a $i
                                svn propset svn:eol-style "CRLF" $i
                                echo invalid extension: $ext

echo "done"

I committed all changes from running this script in changeset 5893.

This is in the openmrs category tagged as , ,


7 Responses

  1. Burke Says:

    Do all source files committed to the repository have to have this property set — i.e., will we have to do this repeatedly over time as new files are added to the repository without the svn:eol-style property set? If so, is there an alternative (permanent) solution — e.g., automatically apply this property to all source files via an svn hook?

  2. Ben Says:

    That is an excellent point, Burke. And I just forgot to mention my solution for that. I added the svn:default-eol-style property to the root folder so that all new files get the CRLF property by default. See http://dev.openmrs.org/browser/openmrs/trunk?rev=5893

  3. The eflow blog » Merge Problems with Inconsistent Newlines in SVN Says:

    [...] the fix_newlines.sh [...]

  4. chase Says:

    Why did we end up doing dos2unix and then CRLF…. that seems wrong. Shouldn’t it have been unix2dos and then CRLF or dos2unix and then LF??

  5. Ben Says:

    I used dos2unix because I just needed a standard line ending before applying CRLF. Yes, it probably would have made more sense to use unix2dos…if I had known it existed.

  6. Adam Bruss Says:

    Thank you very much this worked for me.

  7. Luke Shumaker Says:

    It would have been simpler to use `find` to get a list of files. `find “$path” -type f`

Leave a Comment

Your comment

Please note: Comment moderation is enabled and may delay your comment. There is no need to resubmit your comment.