1. Right click on any Windows Folder
2. Select TortoiseSVN->Setting
3. Click on the ‘Edit’ for Subversion configuration file (which will open the configuration up in Notepad, or something similar).

Unix users can find their config file located in $HOME/.subversion/config and can use any of vim, emacs, nano or pico to edit the configuration (or whatever your personal flavor of editor is).

In either case, once you have opened the file, search for the sections [miscellany] and [auto-props] and then use what follows to make your configuration look similar.


[miscellany]
enable-auto-props = yes

[auto-props]
*.php = svn:eol-style=native;svn:keywords=Id
*.pl = svn:executable;svn:keywords=Id
*.sh = svn:eol-style=native;svn:executable;svn:keywords=Id
*.txt = svn:eol-style=native
*.png = svn:mime-type=image/png
*.jpg = svn:mime-type=image/jpeg
*.gif = svn:mime-type=image/gif
*.xml = svn:eol-style=native
*.xsl = svn:eol-style=native
*.xsd = svn:eol-style=native
*.html = svn:eol-style=native
*.css = svn:eol-style=native;svn:keywords=Id
*.js = svn:eol-style=native;svn:keywords=Id

This sets a couple of svn properties when adding files of the types listed above:

• Adds keyword “Id” (aka $Id$ expansion) to .css, .js, .pl, and .sh files (we can do this for more files if you guys want).
• Set’s the end of line style (CRLF for windows, LF for *nix) to native for every textual file listed (meaning when a windows user checks out the file, they get it normalized to CRLF and a nix user get’s normalized to LF – the normalization happens transparently by your subversion client and internally in the repository they are stored using LF).
• Some files are automatically marked as executable (perl and shell script files)
• Images have their mime-type set appropriately so that subversion knows that files containing those extensions (.gif, .png, .jpg) are binary type files. This has an added benefit of allowing the subversion apache module to send the correct Content-Type header for the file without having to guess.