On Jul 11, 2009, at 04:50, chengjng wrote:
> On 2009-07-11, Ryan Schmidt wrote:
>
>> On Jul 10, 2009, at 02:49, haiqing wrote:
>>
>>> steps:
>>> 1: svn delete B.png (success)
>>> 2: svn add b.png(success)
>>> 3: svn commit -m "add b.png" b.png(success)
>>> 4: in other directory,do: svn co http://1*.*.*.*/svn/ro45/branches/
>>> test_svn_1 (fail)
>>>
>>> result:
>>> the workcopy directory was locked,and can not cleanup success.
>>> A test_svn_1\a.png
>>> A test_svn_1\B.png
>>
>> If this is the same repository location you deleted B.png from above,
>> why is it still there?
>
> I do "svn delete B.png" in the same location ,but not commit it
> to svn server.
> I just commit "add b.png" to server at the same location like
> this: "svn commit -m "add b.png" b.png(success)", so , there are
> b.png and B.png at svn server the same time.
Ah yes, I missed at you were just committing the add of b.png and not
also the deletion of B.png.
So, yes, you have shown a series of steps that put two files into the
repository whose names differ only in their case, and then you try to
check that location out to a case-insensitive filesystem, which
cannot work. If you intend to work with case-insensitive filesystems,
it is an error to commit multiple files to the same repository
location whose names differ only in case, and I recommend you install
a pre-commit hook which would prevent such commits rather than
allowing them to succeed and cause you problems later on. The
Subversion source distribution includes the script case-
insensitive.py which you can use for this purpose.
http://subversion.tigris.org/tools_contrib.html#case_insensitive_py
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2370684
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-07-11 21:13:25 CEST