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

"Skipped obstructing working copy" for folder checked out later from same trunk

From: Marc Preuß <marc.preuss_at_id1.de>
Date: Thu, 14 Mar 2013 08:59:41 +0100

Hi,

when I created my local working copy, I only checked out the projects
I'm working on.
Say, there are folders projectA...projectZ in the SVN trunk.
I created a local folder /projects and used the "Choose items" dialog
to check out only projectA, projectC and projectG.

Later I also worked on projectK so I went to my /projects folder and checked
out projectK. Still, the folder hierarchy is the same as in the trunk, only
that not all folders are there.

/projects
  +-.svn
  +-projectA
  +-projectC
  +-projectG
  +-projectK
    +-.svn

Now when I update /projects I get the "Skipped obstructing working copy"
message for projectK.
I understand that it forms its own working copy because it wasn't
included in my original checkout
and has its own .svn folder. But why does subversion do that when the
folder structure is the same
as in the trunk?

My questions:
- Is there a way to tell subversion that the new folder is part of the
same working copy?
   Or somehow "move" it there, without checking everything out again?
- Is there a way, for a working copy that has originally been checked
out using "choose items",
   to select more items to include when updating, to avoid this
situation in the future?

Am I just not seeing something or are these features really missing?

Thanks,

Marc

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3050992

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-03-14 10:31:15 CET

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.