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

Re: Windows Case Sensativity

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Thu, 03 Nov 2011 20:21:51 +0100

On 03.11.2011 19:54, Sandy Powell wrote:
> I know this has been reported in the past. So I will make it brief. Is
> there a solution around case sensitivities on windows as all? I have
> looked on google and found this issue dating back to Jan 26, 2006 at
> this location
> www.hanselman.com/blog/SubversionCasesensitivityProblems.aspx
> <http://www.hanselman.com/blog/SubversionCasesensitivityProblems.aspx>.

Fixed long, long time ago.

> I have also seen two other mentions of this on the forum but no real
> response:
> http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=859305
> <http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=859305>

That's only for the "Add" dialog. Not really a problem.

> and
> http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=712148
> <http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=712148>.

As you can read in the thread: the auto-renaming works.

> The basic issue I have seen it is that tortoise svn, doesn’t read the
> case correctly on windows at all. This causes whole directories to not
> be usable in source control. The tool is great but because of this issue
> it is unusable for our company. I even found someone was willing to

What exactly is your problem? What doesn't work?

> create a patch here:
> http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=756&dsMessageId=2609682
> <http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=756&dsMessageId=2609682>
> and was told he didn’t follow proper “procedure.” Personally I think a
> patch for an issue over 5 years running would be more important that
> some procedure (not to be sounding angry)… It is just that this is a

*Now* I'm pissed.
Seriously: you link to a thread, then accusing me of rejecting a patch
for no good reason. But apparently you haven't read the thread at all.

First of all: the reason the issue was closed without discussion was
mentioned on our issue tracker main page, and the text is now on our new
issue tracker front page as well:
http://code.google.com/p/tortoisesvn/wiki/IssueTracker?tm=3

So if you don't follow these rules, the issue gets closed. No
discussion. TSVN is a project with thousands of users, if we wouldn't
enforce these policies strictly, we'd end up at the same point like a
few years ago when I had to close the issue tracker for good: I spent
whole evenings just closing invalid issues instead of actually working
on TSVN.

As for the other reason I'm pissed:
if you read the issue tracker entry: it's not a patch, it's an example
program. Second: as we've mentioned repeatedly, this issue can not be
resolved in TSVN but would have to be addressed in the svn library. Sure
that's not mentioned in the issue, because that user never bothered to
search the mailing lists, read our guidelines or do anything at all to
really help.
Third: an example that shows how Windows can deal with case-sensitive
file systems but that requires to change the windows configuration is
simply out of the question. Because if you've ever tried that
configuration you'll notice that many apps that worked perfectly before
start to crash. Now would you consider installing an app that changes
the windows configuration and breaks a lot of your existing apps? I
didn't think so.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2872517
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-11-03 20:22:02 CET

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

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