Ferdinand Soethe wrote: > David Crossley wrote: > > > Ferdinand, will you please configure your SVN client properly. > > This causes too much unnecessary work for someone else, > > usually me. > > > Please follow the instructions at: > > http://www.apache.org/dev/version-control.html#https-svn > > Sorry David. I was unsure whether my current svn-client picked up the > settings correctly so I figured if anything goes wrong I'll fix it > when cleaning up. > > With these things please just throw them back at me instead of fixing > them for me (if possible).
Better to fix it ASAP. Especially with new files because people are more likely to review. The result is mixed line-endings and poor patches. > So how do you tell that something went wrong. In this case, when i edited your document, my editor reported that there were DOS line endings. Usually i run a shell script which interrogates our svn for the properties of each text file. Another script searches for DOS carriage-returns. I try to do this as often as possible but unfortunately too long between. > And what do I do to fix > it apart from reconfiguring tortoise? Use the command-line client :-) but still need to configure it. With most clients you can manually use 'svn propset' before doing 'svn commit', but too tedious. > (In the docs it says only: "However, you should still pay attention to the > messages from your svn client when you do 'svn commit'"). Doing 'svn status' before doing the commit. http://svnbook.red-bean.com/nightly/en/svn.ref.svn.c.status.html With the command-line client, i do 'svn commit' which opens my editor for log message, it reports the files that have been changed in the same format as does 'svn status'. Properties are flagged in the second column. If there are none for new text files they you know its busted. Text files should get the 'svn:eol-style native' property. Do 'svn proplist --verbose myFile.txt' to see. -David
