BTW, I also noticed that 'svn log' ignores case on Windows, even though none
of the other commands seem to. Makes it hard to reconstruct history when
recovering from something like this.
-----Original Message-----
From: John Barstow [mailto:John_Barstow@gfsg.co.nz]
Sent: Monday, 30 June 2003 10:15 a.m.
To: 'Garrett Rooney'
Cc: Subversion Dev (E-mail)
Subject: RE: Case-sensitivity and Windows
> No, there isn't a switch or configuration option to handle it. There
> are just too many filesystem dependent special cases that we don't
> bother trying to handle them.
Granted, but if we're deliberately not handling them can we document
fixes/workarounds for the ones we are aware of? That way those of us using
a fringe OS like Windows at least know what's going on. It took me the
entire weekend to figure out why I was getting an 'update obstructed',
especially I had upgraded to 0.24.2 the day before. And now I have coax our
web person into trusting our source control again.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jun 30 00:19:02 2003