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

Re: case insensitivity revisited

From: James M. Lawrence <quixoticsycophant_at_yahoo.com>
Date: 2006-10-26 19:47:55 CEST

> (a) the svn client could treat foo.h and Foo.h the same.

I was hoping to get a response to this option. What if the svn client
had an option (perhaps a compile option) which would cause this to
never happen:

    enkidu% svn status
    ! Foo.h
    ? foo.h

I understand that depending on case-insensitivity is wrong. It
wouldn't happen if it were my code. But it's not my code; I'm porting
a relatively large existing code base. I plan to reformat my hard
disk with a case-sensitive (non-boot) partition, but I cannot do that
right now.

In the meantime, what would be the harm of an svn client option for
which the above 'svn status' reports no change? It would merely be a
stop-gap measure to help developers stay productive, and would be
advertised as such. It would not be the default behavior.

Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Oct 26 19:49:26 2006

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.