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

RE: Explorer Copy Issues

From: Fisher, John <jfisher_at_forthrightsolutions.com>
Date: Thu, 15 May 2008 14:24:59 -0500

There really isn't anything "new" when you copy Directory_B and name it
Directory_C. Subversion looks at the directory, see's that it's already
connected to Subversion and then looks at the files, which haven't
changed. All you've accomplished is making 2 working copies of the same
repository location.

If you were to disconnect Directory_C from subversion (one method is to
remove the ".svn" folder inside it), then subversion would see the
directory as being "unversioned" and allow you to treat Directory_C and
its contents as "new".

It may help to think of each directory as a totally separate entity,
with subversion checking the files inside that folder. With that sort
of mental model, you can see that checking in sub-folders is merely a
feature of the software to make nested imports easier. Each folder
knows where its files belong in subversion, so your local directory
structure could be completely different from the subversion repository
structure. (I don't suggest you work that way, though!)

John

-----Original Message-----
From: Matt (MPCM) [mailto:WickedLogic_at_gmail.com]
Sent: Thursday, May 15, 2008 2:06 PM
To: users_at_tortoisesvn.tigris.org
Subject: Explorer Copy Issues

I've hit a bit of a weird order of events (bug?) when copying a folder
that is part of the repository already, and using that as a starting
point for parallel future modifications. I understand why within that
folder (and sub folders) it might not show differences, after all
the .svn data matches, but it seems like the parent folder should be
able to say 'hey, there's a new folder here', or perhaps a bit further
and say 'hey, the sub folder svn data doesn't match the path I thought
it would have'.

Wanted to see if this is a misconception of mine. This is the only
confusing item I have hit so far with it.

Example:

Directory_A\
  Directory_B\
    File_A_B

If I copy File_A_B it can tell there is a new file. If I copy
Directory_B, paste it in Directory_A, and call it Directory_C.
Directory_A still retains checked and a commit shows now new files.

Directory_A\
  Directory_B\
    File_A_B
  Directory_C\
    File_A_B

Is there a reason the data related to Directory_A doesn't cause
Directory_C to be flagged? I understand a commit from either B or C
would update the repo's B, I keep feeling like I'm not understanding
why this is happening.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-05-15 21:28:28 CEST

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