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

RE: svn switch question

From: Bicking, David (HHoldings, IT) <David.Bicking_at_thehartford.com>
Date: 2007-11-01 20:25:35 CET

> -----Original Message-----
> From: Miller, Eric [mailto:Eric.Miller@amd.com]
> > I am a bit confused by the question. Are you saying that you have
> these
> > paths as a single working copy, then "switched" C and A to tags
> > elsewhere in the repository, then deleted C from the
> repository? Is
> > "path" a subfolder of trunk and tag1 and tag2 subfolders of tags?
> Yes. This is the working copy:
> path/ => trunk/path
> path/A => tags/tag2/path/A
> path/B => trunk/path/B
> path/C => tags/tag1/path/C
> In a revision after tag1 was created the path trunk/path/C
> was deleted.
> Now I want path/C to be the same as trunk/path/C (deleted)
> without affecting path/A.
> If I did a 'svn sw trunk/path path' then path/C would get
> deleted, but it also forces path/A to the trunk as well,
> which I need to avoid.
> Eric

First, my opinion on this: Rethink your methodology. I don't think it
is a good idea to have a single working copy reference items from
multiple branches while looking/acting like a representation of "trunk".
Presumably, when you commit, these changes are going back to their
respective locations in the repository anyway (since you switched the
subfolders, so this is just a working copy convenience to you, right?

Now, I suggest that if you wish to continue doing it this way that you
make each path (A, B, C) its own working copy (checkout each
separately). If you'd done this before, you'd simply delete the "C"
working copy and be done with it. The disadvantage is that you would be
doing a commit per path, rather than a commit at the root, but it would
more accurately represent what is actually happening.

This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information. If you are not the intended
recipient, any use, copying, disclosure, dissemination or distribution is
strictly prohibited. If you are not the intended recipient, please notify
the sender immediately by return e-mail, delete this communication and
destroy all copies.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 1 20:26:27 2007

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.