Re: commited delete with uppercase/lowercase filename, what to do?

Your workspace is on a Windows system. What is your server? Windows servers
are case insensitive.

If your backend is Linux, it is extremely likely that your repository always
contained both "filename.ext" and "fileName.ext", but you never saw the
latter because the former always mapped over it. Not you deleted
"filename.ext", you're finally seeing "fileName.ext".

On Fri, Aug 14, 2009 at 3:27 AM, Markus Kropf <m.kropf_at_computer.org> wrote:

> Hi,
> I updated my workspace, then committed my changes. My commit included a
> delete of the file "filename.ext".
> Later, i saw that the update had put the file "fileName.ext" in may
> workspace. Now the repository contains
> my delete "filename.ext", but such a file does not exist, because it is
> actually "fileName.ext".
> Should sound familiar to you, probably something many Windows user
> experienced...
> What do I have to do now? Is that erroneous delete a problem? How can I get
> rid of it? Do I have to fix the repository in some way?
> Thanks for your help
> Markus Kropf
>

-- 
David Weintraub
qazwart_at_gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2383637
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].