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

RE: broken file name handling

From: Paul Charlton <techguru_at_byiq.com>
Date: Tue, 30 Sep 2008 11:09:27 -0700

I can confirm that the current windows client is seeing the "?WHAT?.txt" when checking out root. (both Tortoise and Collab.Net command line client).

If it has been previously reported on this list, is there an open bug report?

thanks,
Paul

-----Original Message-----
From: Branko Čibej [mailto:brane_at_xbc.nu]
Sent: Tuesday, September 30, 2008 10:41 AM
To: Paul Charlton
Cc: 'Karl Fogel'; dev_at_subversion.tigris.org
Subject: Re: broken file name handling

Paul Charlton wrote:
> Karl,
>
> Thanks for researching that ... but it does not explain how the bad name
> ever got into the Windows working copy. We started with an empty working
> copy, and simply did "svn co URL/" to create the wc from the remote repo.
> At some point, the "svn co" failed with the error noted below, and ever
> after the "svn up" reproduces the same message. The behavior is different
> (and correct) if you begin with "svn co URL/mk.xiv/" ... (ie: checkout
> project vs checkout root)
>
> The undesired behavior is totally reproducible on the SVN repository itself
> and was pointed out to me by a colleague.
>

This is clearly wrong and has been reported before on this list, IIRC. A
client that checks out the HEAD of the root of our repository should
never see that old ?WHAT?.txt mentioned, ever.

-- Brane

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-09-30 20:09:43 CEST

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.