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

Stefan Küng wrote:
> h.larsen@risoe.dk wrote:
>
>> Stefan Küng wrote-->
>>
>>> Not really. TSVN can't know that you have another working copy, and
>>> it can't know *where* that working copy is located. We could try to
>>> list all files in the repository before every commit, but that
>>> would just take too long a time ('svn ls' isn't very fast).
>>
>> Would you think the implementation of a pre-commit hook to check for
>> conflicting filename case, would suffer similar performance problem?
>
> No. The hook script has local access to the repository and is a *lot*
> faster in that area. Of course, if you have a very big repository, it
> still can take a few seconds for the check to finish.

Confession time.

The script isn't as efficient as it should be, improving it is on my
TODO list, but as I am not well aquainted with Python or the Subversion
API's it will take me some time to do.

The speed depends on where files are added in the file tree. If you
have a deep tree and add a file at the top the script will extract the
names of all the files in the tree when it only needs the names of files
in the current directory. This can take a while.

-- 
Martin Tomes
echo 'martin at tomes x org x uk'\
  | sed -e 's/ x /\./g' -e 's/ at /@/'
Visit http://www.subversionary.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org