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

RE: [TSVN] case-sensitive filename conflict on commit. How to testthis?

From: <h.larsen_at_risoe.dk>
Date: 2005-09-30 17:07:21 CEST

>> We had such a situation with different team members. John had added
>> "resource.h" and commited, and Mike added "Resource.h" later without
>> updating first. After that, we had both files in the repository.
>>
>> However, this was also with an older TSVN version, I don't know if
the
>> current version would detect that.

> That might be it, yes. That's the only way I can think of where TSVN
> simply can't adjust the 'wrong' case in filenames because it doesn't
> know that there's another file with the same name in the repository.

> And it can't be a 'old' version: that check/correction was added way
> before 1.2.

Brilliant, I just tested this on 1.2.4, and it does exactly that: Allows
commit of resource.h and RESOURCE.H without any hick-ups. You don't have
to be different users, just checkout two WC's to provoke it.
The hook
http://svn.collab.net/repos/svn/trunk/contrib/hook-scripts/check-case-in
sensitive.py.
catches this ofcourse.
Aren't there anything TSVN could do to help out on detecting this
conflict?

henning

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Sep 30 20:41:39 2005

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