AFAIK, in normal circumstances you should not have to do a propset at all. The server is already configured to accept the usual text files as as eol-style=native.
Problems occur when the first commit is non-standard. If so, svn does not treat the file as eol native, and only then do you need to propset. So the main thing is to ensure that the files are correct when first added. On Sat, Feb 26, 2011 at 2:53 AM, David Mitchell <[email protected]> wrote: > Yes, I had reviewed that page on the wiki earlier. The only references I > found > to eol settings were: > > Teach svn to convert unix/dos line ending for text files. > > and > > Add the new subdirectory into svn, and then commit the changes. For example, > in > a command window: > > I had created the entire set of addon repository directories via SVN from the > J > repository. I was not creating a new addon directory, just adding two ijs > files > to an existing addon directory. > > It wasn't clear to me that I should do a propset for a directory I had not > created. > > I had previously looked in the tortisesvn help and I had found the entry on > auto-props and updated the svn config file with: > > [auto-props] > *.java = svn:eol-style=native > *.ijs = svn:eol-style=native > *.sh = svn:eol-style=native > *.bat = svn:eol-style=native > *.ldif = svn:eol-style=native > *.txt = svn:eol-style=native > *.xml = svn:eol-style=native > *.html = svn:eol-style=native > > But, this was done after I had already created the files in the svn-created > directory and added them to svn. > > Looking at the files now, they do not have the > > svn:eol-style native > > property that all of the svn-created files in the misc directory have. > > On 2/25/2011 9:09, bill lam wrote: >> Please refer to jwiki >> http://www.jsoftware.com/jwiki/Addons/Developers%20Checklist >> >> for svn propset, I also amended it to include jproj and htm(l) files. >> >> If you use tortoisesvn, it will be even simpler as it has a auto-prop in >> its configuration setting to automatically propset for new files. >> >> I'll do another svn propset again for the whole svn, please checkout to >> make it take effect. >> >> Птн, 25 Фев 2011, David Mitchell писал(а): >>> My apologies. I'll move over to the sandbox repository and see if I can >>> puzzle >>> out what is needed to get svn to perform the conversion automatically. I >>> had >>> hoped to use tortisesvn, but it does not seem to make this simple to do. >>> >>> On 2/24/2011 21:26, bill lam wrote: >>>> It will help if you could write a short commit message for each commit, >>>> otherwise the log might look like in git >>>> >>>> f4fb07b git-svn-id: http://www.jsoftware.com/svn/addons/trunk@2527 >>>> 7b1320e8-e022-0410-a07a-c339c07ae202 >>>> c539b2a Fix 64 bits args and UTF8 file names. >>>> 3c68200 git-svn-id: http://www.jsoftware.com/svn/addons/trunk@2523 >>>> 7b1320e8-e022-0410-a07a-c339c07ae202 >>>> 4e50e21 Fix EOL >>>> 1cc47c0 git-svn-id: http://www.jsoftware.com/svn/addons/trunk@2519 >>>> 7b1320e8-e022-0410-a07a-c339c07ae202 >>>> 5e9d36b Minor fix >>>> 14d64cb Add clippaste.ijs and test_clippaste.ijs >>>> 0024436 math/lapack: fix test0.ijs >>>> >>>> I can see you need to fix EOL again, did you propset the eol style last >>>> time? Window users should be able to use CRLF in their local checkout, >>>> the conversion to/from LF is automatic during svn update and svn commit. >>>> >>>> Чтв, 24 Фев 2011, David Mitchell писал(а): >>>>> Yes, you are correct, some i's should be (and now are) x. >>>>> >>>>> setclipfiles now handles Unicode names. >>>>> >>>>> On 2/24/2011 0:40, bill lam wrote: >>>>>> EOL now looks good. >>>>>> >>>>>> Perhaps there are 2 more issues, >>>>>> >>>>>> 1. usually window handles are 64-bit in x64, some i might need change to >>>>>> x. >>>>>> 2. non-ascii file names may not work in setclipfiles >>>>>> >>>>> ---------------------------------------------------------------------- >>>>> For information about J forums see http://www.jsoftware.com/forums.htm >>>> >>> ---------------------------------------------------------------------- >>> For information about J forums see http://www.jsoftware.com/forums.htm >> > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
