On Tue, Jan 5, 2010 at 04:38, Simon Large
> 2010/1/5 muhammad salman khan <hmsalmankhan_at_gmail.com>:
>> Dear Valueable Administrator,
>> We are currently using Torotise SVN 1.6.2 version in my Company there we are
>> facing some kind of issues in this software just like
> There have been several bug fixes since 1.6.2. Please update to 1.6.6
>> --> check for midification... option in right down area if folder property
>> change this is treat as files like MODIFIED: 14 files that include also
> I don't understand this. Please try again to explain what you mean.
>> --> if we remove cache then log retrieving time of so painfull
> What is the problem? If you turn the cache off or delete the cache
> content then access is slow. That is what a cache is for.
>> --> I know this is case sensitive. but when we access the repository with
>> wrong name case (Like: Live-Code --> live-code )it can be access but we
>> cannot modify in repository mean it access in READ-ONLY mode.
> That is a known feature/bug of the subversion *server* not the client.
> You need to ask on the subversion mailing list about this one.
It's barely even the Subversion server - it's really Apache & Windows.
Apache on Windows allows you to access repositories (using
SVNParentPath) in a case-insensitive manner because Windows is
case-insensitive. The OP has unlimited read access to the repository,
but when mod_dav_svn checks permissions for the commit, it's looking
for a rule which matches live-code because that's where he checked out
from, but only finds rules for Live-Code; the rules ARE case-sensitive
because Subversion is case-sensitive everywhere.
Solution at the client side is to use svn switch to point at the
properly-cased URL. On the server side, use a case-sensitive host OS
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-01-05 13:42:47 CET