Re: Subversion problems on windows
On 08 Feb 2006 14:47:32 -0800, Derek Zhou [EMAIL PROTECTED] wrote: Yes, remove them all! All sane editors under windows can cope with unix style LF automatically anyway. I don't think anybody here is using notepad or vc.net, right? Will removing all of these hurt anyone? I've got a list of 7654 files in /devmodules with the property set and am just waiting for the word. - Andy ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Fwd: Subversion problems on windows
On Thu, Feb 09, 2006 at 08:07:04PM +, Richard Frith-Macdonald wrote: It screws up my editor on text files... makes it a pain to try and do anything when using mingw/msys. I would like to see eol-native removed from ALL files. Sure thing. I will do it shortly, don't be alarmed when you see a 7654 files changed commit ;) - Andy -- Andrew Ruder http://www.aeruder.net ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Subversion problems on windows
On 9 Feb 2006, at 14:38, Jeremy Bettis wrote: Derek Zhou wrote: Andrew Ruder [EMAIL PROTECTED] writes: Yes. The svn:eol-native property needs to be removed from the files. I can do this, but I am curious which data files it is messing up? But if none of the files need this property (I was under the impression it was standard operation with CVS), I will go through and remove them all. Yes, remove them all! All sane editors under windows can cope with unix style LF automatically anyway. I don't think anybody here is using notepad or vc.net, right? Derek I disagree. The svn:eol-native property is good! It also keeps the CR characters out when new commits are done. Just don't set that property on non-ascii files. It screws up my editor on text files... makes it a pain to try and do anything when using mingw/msys. I would like to see eol-native removed from ALL files. ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Subversion problems on windows
Jeremy Bettis [EMAIL PROTECTED] writes: Derek Zhou wrote: Yes, remove them all! All sane editors under windows can cope with unix style LF automatically anyway. I don't think anybody here is using notepad or vc.net, right? Derek I disagree. The svn:eol-native property is good! It also keeps the CR characters out when new commits are done. Just don't set that property on non-ascii files. Most sane Unix editors can cope with windows CR/LF automatically too; as long as no one is mixing styles in the same file, everyone should be fine. If the style is mixed up within the same file, even eol-native can not guranty to do the right thing anyway. My suggestion is the origin author of a file decides which style this file should be, be it windows or unix or mac, and everybody just follow the convention within this file. Having to keep track of which file is ascii and which file is binary is tedious. Derek ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Subversion problems on windows
Derek Zhou wrote: Most sane Unix editors can cope with windows CR/LF automatically too; as long as no one is mixing styles in the same file, everyone should be fine. If the style is mixed up within the same file, even eol-native can not guranty to do the right thing anyway. My suggestion is the origin author of a file decides which style this file should be, be it windows or unix or mac, and everybody just follow the convention within this file. The trouble with using the svn:eol-native property is that it makes subversion do a line conversion. So it does the unix2dos or dos2unix conversion. So your suggestion of letting the author decide and everybody else just stick with that can only be done if the property is *not* set. Otherwise you check out a file and it's always native to the platform you checked out on. Having to keep track of which file is ascii and which file is binary is tedious. Agreed and there is no need to do that if we delete the propery. Note though, that we'd otherwise need to keep track of which file is considered 'text' by subversion but is encoded non-ascii. Regards, Sheldon ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Subversion problems on windows
Sheldon Gill [EMAIL PROTECTED] writes: Derek Zhou wrote: Most sane Unix editors can cope with windows CR/LF automatically too; as long as no one is mixing styles in the same file, everyone should be fine. If the style is mixed up within the same file, even eol-native can not guranty to do the right thing anyway. My suggestion is the origin author of a file decides which style this file should be, be it windows or unix or mac, and everybody just follow the convention within this file. The trouble with using the svn:eol-native property is that it makes subversion do a line conversion. So it does the unix2dos or dos2unix conversion. So your suggestion of letting the author decide and everybody else just stick with that can only be done if the property is *not* set. I am arguing against svn:eol-native too. :) IMHO, server side processing of source files is potentially harmful; I am even against svn:keywords. Derek ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
