On Thu, Jun 3, 2010 at 7:19 PM, Geert Janssens <[email protected]>wrote:
> On Wednesday 2 June 2010, Christian Stimming wrote: > > (But only for files which are already in SVN. New files will always have > no > > svn:eol-style set. It is not possible to have those set for new files by > > the server automatically. Believe me, it is not possible - I have spent > > considerable time researching this. The only simple workaround is that > all > > developers modify their $HOME/.subversion/config files and activate the > > following lines: > > > > enable-auto-props = yes > > *.c = svn:eol-style=LF > > *.h = svn:eol-style=LF > > *.sh = svn:eol-style=LF > > > > Once this is set on a user's computer, every new file that is added to > svn > > from that computer will have the noted eol-style property added > > automatically.) > > > I suppose this configuration only caters for files ending in .c, .h or .sh > ? > So if I add such config file and then add a new patch file (ending in > .patch > or .diff) those files would still have undetermined line endings... > > We'll just have to be vigilant then when adding new files, right ? > How about also set ".patch and *.diff to 'LF'? I checked those .patch and .diff, most of them are patches for .c, .cpp, Makefile and autotools files. I think it should be ok to set them to 'LF'. -- Regards Tao Wang _______________________________________________ gnucash-devel mailing list [email protected] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
