> -----Original Message-----
> From: Steven Bakke [mailto:steven.bakke@amd.com]
>
> 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
> >
> 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
>
Perhaps, but I still can't wrap my head around why he needs to do this.
I can't answer his question, either, because I don't think what he wants
is possible. I suspect my problem with this is due to the number of
years I've been working on Java or DotNet style projects. Generally, I
don't see any value in arbitrarilly switching subprojects around. Maybe
in a more low-level environment, like C, where such rigid
project/package definitions don't exist, this kind of mixed bag is more
logical.
Unfortunately, I have to step back from this problem because I cannot
offer any constructive ideas. I do want to understand the reason for
this scenario, though.
--
David
*************************************************************************
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 Fri Nov 2 14:12:40 2007