[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: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-04-13 14:00:32 CEST

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
moment, the update stops and says "whoa, there's a modified file in the
directory I'm trying to delete." The fact is, however, the directory
has already been "removed from version control". It's no longer
mentioned by any .svn/entries file; when the update stops, all you have
is an unversioned directory containing single path(s) that wind their
way down to modified or unversioned files. The directory has been
"gutted". If you run 'svn up' again, it will continue where it left off
and complete the update just fine.

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.

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:01:31 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.