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

RE: Changing Case / svn move

From: Stuart Celarier <SCelarier_at_corillian.com>
Date: 2006-06-01 18:21:03 CEST

Meaning no disrespect, Markus, but I did read your proposal [1]
carefully several times. You don't mention the server or the client,
much less distinguish where you propose to make changes.

You stated the problem as "changing case of a filename" and cite svn
move as an example of the problem. That makes it sound like you are
trying to solve the general problem of the mismatch between case
sensitive Subversion and case insensitive Windows file systems.

Here are a couple of suggestions.

This belongs on the Subversion developers list.

Clearly state the problem you are trying to solve. In this case, you
appear to only be interested in the svn move operation in a working
copy, not in the repository. There are many symptoms of case
sensitivity/insensitivity mismatch, so saying "as we all know" doesn't
help pinpoint what your proposal is about.

If you are proposing a change to the svn.exe client, you should consider
whether this change can, should, or must be made for all Subversion
clients (e.g., TortoiseSVN), and if so, how is that accomplished?

It's not clear what you have in mind when you say that an "isWindows"
option could be set by an admin. Our admins deal with the Subversion
server, not the clients.

If you are not aware of some the recent discussions of the svn move
operation in the developer list (e.g., moving a moved file [2], etc.)
you might want to read up on those.


Stuart Celarier | Corillian Corporation

[1] http://svn.haxx.se/users/archive-2006-05/1450.shtml
[2] http://svn.haxx.se/dev/archive-2006-05/0428.shtml

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 1 18:23:38 2006

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

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