I use a lot of Cygwin tools (make, ediff, etc.) for developing and
building the JDEE on Windows. In the past, I have had trouble with
Windows line endings when using these tools. It's possible the Cygwin
has resolved these issues but if not, the change you propose might
affect me adversely.
I have never had any problem working with files with Unix line endings
on Windows, even with native Windows apps, such as Araxis Merge. Thus,
unless there is some demonstrable advantage to using Windows line
endings, I'd prefer that svn deliver JDEE text files with Unix line
endings to my Windows sandbox.
> -----Original Message-----
> From: jdee-devel-bounces@... [mailto:jdee-devel-
> bounces@...] On Behalf Of Len Trigg
> Sent: Monday, January 14, 2008 6:01 PM
> To: jdee-devel
> Subject: [jdee-devel] svn:eol-style native
> svn has a property that allows you to specify that "textish" files use
> platform native line endings. This is not currently set for the files
> in the repository. In my sandbox I have set this property on the
> appropriate files. Since currently the code seems to use unix line
> endings, it'll mean that people using windows will get windows line
> endings. If no-one objects (e.g. because maybe some windows diffing
> tools / scripts etc depend on the unix endings?), I'll commit the
> When you add files to svn, you can also get it to automatically set
> this property (and others) for certain types of files. On unix, you
> do this by editing your ~/.subversion/config file such that
> enable-auto-props is set to yes, and adding lines to the [auto-props]
> section such as:
> *.java =3D svn:eol-style=3Dnative;svn:keywords=3DRevision
> *.sh =3D svn:eol-style=3Dnative;svn:executable
> *.txt =3D svn:eol-style=3Dnative
> *.el =3D svn:eol-style=3Dnative
> *makefile =3D svn:eol-style=3Dnative
> There is no doubt an equivalent method on windows.
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> jdee-devel mailing list