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

Re: Renaming files on win32

From: <brane_at_xbc.nu>
Date: 2004-12-22 22:48:55 CET

Scott Palmer wrote:

>
> On Dec 22, 2004, at 4:02 PM, brane@xbc.nu wrote:
>
>> Gili wrote:
>>
>>> On Wed, 22 Dec 2004 20:16:08 +0100, Erik Huelsmann wrote:
>>>
>>>> What's your proposal?
>>>
>>> The server should store all paths in a case-sensitive manner.
>>
>> Already does that.
>>
>>> All clients (regardless of the platform) should be aware of concerns on
>>> other platforms
>>>
>> No. We already decided not to do that, because file naming
>> conventions are project policy, not repository constraing.
>
> ....
>
> I was actually just proposing that the rename be made to work on Windows.
>
> At eh beginning of this thread it was said:
>
> you can't _directly_ rename "Abc" to "abc".
>
> On windows if you have a file "Abc" and you rename it to "abc" in the
> local filesystem it just works. There is no reason to not allow this
> as long as something named "file" does not already exist in the
> working copy which is impossible on Windows anyway. It seems there is
> a bug in Subversion in that it tries to access "abc" -- which on
> windows successfully accesses "Abc", and then Subversion gets confused
> about the existence of the target name, when it fact it is detecting a
> bogus conflict with the source name.
>
> Surely THAT can be easily fixed?

See my other post. It can and should be fixed, but I'm not sure about
the "easily". And I for one certainly won't accept a solutiion that
works in some locales but not in others. A solution that works on /all/
case-insensitive file systems would be favourite.

- Brane

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Dec 22 22:53:24 2004

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

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