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

Re: FAQ suggestion/question

From: Duncan Murdoch <subversion_at_murdoch-sutherland.com>
Date: 2004-08-20 18:37:16 CEST

On Fri, 20 Aug 2004 12:09:42 -0400, Nathan Kidd
<nathan@hummingbird.com> wrote :

>kfogel@collab.net wrote:
>> Duncan Murdoch <subversion@murdoch-sutherland.com> writes:
>>>How should I have done this? It shouldn't be necessary for every
>>>Windows user to do commits to the repository to update their checked
>>>out version, and asking for a new checkout seems a little extreme....
>> Sadly, the best recommendation I can think of is to blow away the
>> directory (using standard operating system recursive removal, I don't
>> remember the exact command for Windows) and then update. Sorry for
>> the inconvenience.
>And then prevent it from happening again by adding the
>check-case-insensitive.pl script to your pre-commit hook.
>Find it in http://svn.collab.net/repos/svn/trunk/contrib/hook-scripts/
>or a svn source tarball.
>FYI I'm currently modifying this script to fix performance when adding
>to the root of large trees. I plan to submit a patch to the dev list soon.

We already know to avoid having files with clashing names in the
project. The problem here is changing from one form to another: we
wanted "README" instead of "readme". A script shouldn't prevent a
change like that, and SVN shouldn't get confused by it.

It's not as though case-insensitive file systems are a new invention.

Duncan Murdoch

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 20 18:37:37 2004

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.