Ummmmm please do _NOT_ commit all your sandboxes! If anything we are trying to _stabilize_ the codebase! Release is coming soon let's not break anything!
As for line endings: yeah it's gotten quite annoying because if you actually make a change in the editor, then remove what you added, it will leave the different line endings, as was the case on some of my commits (I would add a debug statement, and kill it later, but the files still looked modified to SVN but alas I was lazy. The right combination of properties needs to be figured. First, we're going to need a sweep of the trunk where all text files get the svn property eol-style=native, which willl make SVN treat both \n and \n\r as line endings and convert them to the user's native line endings when they check out. Then, we need a participatory effort from all the developers to enable automatic property adding when a file is added to the repository. For the stock Subversion on UNIX, put this in your ~/.subversion/config: [miscellany] enable-auto-props = yes [auto-props] *.cs = svn:eol-style=native *.txt = svn:eol-style=native *.skm = svn:eol-style=native *.xml = svn:eol-style=native *.csproj = svn:eol-style=CRLF If you can think of some more formats, please go for it. As for those using TortoiseSVN or other GUI-based solutions, hopefully this is supported by those, I don't know. Bruce? -- fury long name: William Lahti handle :: fury freenode :: xfury blog :: http://xfurious.blogspot.com/ ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ SharpOS-Developers mailing list SharpOS-Developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sharpos-developers
