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

RE: Unversioned files in working copies

From: Nicklas Norling <nicklas.norling_at_ifsab.se>
Date: 2004-04-13 14:13:55 CEST

> -----Original Message-----
> From: Ben Collins-Sussman [mailto:sussman@collab.net]
> Sent: den 13 april 2004 14:01
> To: John Peacock
> Cc: Jan Evert van Grootheest; Markus Wolff; subversion-user
> Subject: Re: Unversioned files in working copies
> John Peacock wrote:
> > The way to unblock the commit is to move away the directory in WC2
> > that
> > is missing in the repository and let the remainder of the update
> > proceed. Then WC2's owner takes a stick and asks WC1's owner why a
> > directory under active development was deleted without warning. ;~)
> That's exactly right. But let me add to that explanation. At the
> This behavior is about to change, however. Karl and I have been
> reviewing Ram's patch for issue #1806. When we commit this, it means
> that 'svn up' won't actually stop at all. You'll see a
> message during
> the update about the directory being removed ("D dir"), but
> after the
> update completes, the directory might still exist as a hollowed-out
> unversioned thing. It becomes a chunk of unversioned data.

Wow! That's great news, I'm seing way to much wierd WC "corruption"
occuring after our cvs->svn conversion. Sounds like this might solve
a few problems.

As a matter of fact, I'd love to see this (or any WC "corruption" fixes)
as soon as possible if that isn't too much to ask for?
May we see it in 1.0.2?

Great work!


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Apr 13 14:43:23 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.