Donald H Locker wrote:
> What I'm trying to do is create a tag for a release that includes files
> (typically a half-dozen to a dozen files) that were switched from the
> directory's natural repository.
>
> e.g. dir1/ file://repo1/trunk/dir1
> dir1/moo file://repo1/trunk/dir1/moo
> dir1/oink file://repo1/trunk/dir1/oink
> dir1/tweet file://repo1/branches/birds/dir1/tweet
>
> When I tag this directory, tweet in the tag from
> file://repo1/trunk/dir1/tweet so it doesn't really reflect the build. That
> is, when I check out the tag, tweet is identical (modulo svn:keywords) to
> trunk/tweet.
>
> When I make a branch for tweet and switch all of dir1 to that branch, I
> have
> to remember to [regularly] synch moo and oink deltas from the trunk.
> Obviously there are many more sounds in the barnyard and surrounds than I
> have used in this illustration, and that makes the problem a bit daunting
> for me.
>
Personally, what I would do is set up release branches... merge in
whatever you need from the trunk and/or other branches... then tag and
release from your "release branch".
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Mar 14 22:59:10 2007