[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Question re auto-props example in config file

From: Thomas Heller <theller_at_ctypes.org>
Date: 2007-03-01 20:59:10 CET

Kylo Ginsberg schrieb:
> The default .subversion/config file contains some helpful examples in
> the auto-props section. Here's a snip:
> *.c = svn:eol-style=native
> *.dsp = svn:eol-style=CRLF
> Makefile = svn:eol-style=native
> My question is: why single out *.dsp for an svn:eol-style of CRLF?
> By way of background, I have a lot of directories representing
> libraries built both with Visual Studio in a Windows environment and
> with gnu tools in a Unix environment. So a sample directory might
> include:
> lib/foo.c
> lib/Makefile
> lib/foo.dsp
> My thinking would be to make all 3 of these files, .dsp included, set
> svn:eol-style to native. That way, a developer on either side needing
> to make a simple mechanical change (e.g. renaming foo.c to foo1.c)
> could edit both respective build files in their env, and check them in
> safely.
> But the sample config singles out *.dsp. Am I missing something? Is
> there a workflow where it would cause troubles if these are all set to
> native?

Visual Studio refuses to load .dsp files that have the wrong line endings;
so this setup is entirely correct. Problems would occur with native line
endings if you build a source tarball on a Linux platform, and try to use that
on a Windows machine.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Mar 1 21:05:47 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.