On Nov 1, 2007, at 3:25 PM, Bicking, David (HHoldings, IT) wrote:
>> -----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?
>
This is the perfect scenario for tags which are 'labels' rather than
cheap copies. It really illustrates how cheap copies really are
different from labeling an arbitrary set of revisions. A lot of
people would be happy if labels existed such that acrobatics such as
decribed above would not be necessary.
-steve
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 1 21:39:03 2007