[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: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2005-10-02 09:57:56 CEST

h.larsen@risoe.dk wrote:

> 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?

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).


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sun Oct 2 09:58:10 2005

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

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