I have a feeling you will also need the 'miscellany' section I posted, as that looks like it is just based on the stock SVN client and has the same config syntax. Cool :)
On Dec 30, 2007 8:12 PM, Bruce Markham <[EMAIL PROTECTED]> wrote: > > > > On Dec 30, 2007 7:45 PM, William Lahti <[EMAIL PROTECTED]> wrote: > > > 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! > > > Maybe by "clean" he meant just making sure we deleted old stuff? *shrug* > > > > > > 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. > > Yea, I think this has gotten in my way a couple times. Luckily with > TortoiseSVN, I can just revert the imaginary change, before I commit. But I > won't say I'm not guilting of letting this slip by me... > > > > > > 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. > > > If I have time tonight after my code cleanup, I'll write a quick C# program > to make a sweep for us and ensure that the property is everywhere. (Unless > you can write a bash script to do it, for which I'd be grateful...) > > > > > 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? > > > > I had never heard of auto-props before, but I learn something everyday > around here, it seems. > The following instructions are ripped from > http://www.mail-archive.com/[EMAIL PROTECTED]/msg10022.html . > (Some editing performed by yours truly.) > > > > > > 1. Right click on any Windows folder > > 2. Select TortoiseSVN->Settings > > 3. Click on the 'Edit' for Subversion configuration file > > > > Inside Notepad find the [auto-props] section, and paste the > > following instead the current one: > > > > > > ### Section for configuring automatic properties. > > [auto-props] > > ### The format of the entries is: > > ### file-name-pattern = propname[=value][;propname[=value]...] > > ### The file-name-pattern can contain wildcards (such as '*' and > > ### '?'). All entries which match will be applied to the file. > > ### Note that auto-props functionality must be enabled, which > > ### is typically done by setting the 'enable-auto-props' option. > > > > *.cs = svn:eol-style=native > > *.csproj = svn:eol-style=native > > *.sln = svn:eol-style=native > > *.build = svn:eol-style=native > > *.sh = svn:eol-style=native;svn:executable > > *.bat = svn:eol-style=native;svn:executable > > *.cmd = svn:eol-style=native;svn:executable > > > > *.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 > > *.config = svn:eol-style=native > > *.html = svn:eol-style=native > > *.jsp = svn:eol-style=native > > > > > > > *.skm = svn:eol-style=native > > Makefile = svn:eol-style=native > > CHANGELOG = svn:eol-style=native > > > > > README = svn:eol-style=native > > > I'd post it on the Wiki, but it should really go in with coding guidelines > and the like. > ------------------------------------------------------------------------- > 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 > > -- 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
