Chris Lambrou wrote:
> As you suggest, I also work on only a subset of the repository, but
> the problem still exists. The
> project I'm currently working on has
> become fairly large, so I only have the trunk and one branch
> checked
> out. For the most part, the small group of developers also working on
> this trunk tend to keep
> to their own sub-folders of interest and
> responsibility, but we frequently overlap, working anywhere
> within the
> trunk as required. One of those sub-folders contains a fairly large set
> of database script
> files, and it would be nice to be able to label
> this sub-folder before I embark on any substantial
> changes to the
> scripts. I would consider these labels to be my own, private labels,
> that don't really
> concern any of the other developers working in the
> same trunk. At the moment, if I create such a label
> using a local
> tag, every other developer working on the trunk gets a copy of this when
> they next
> update, which takes quite a long time because the scripts
> are large.
Could you show us the structure of your repository, because I, for one,
completely fail to understand your problem.
For example, here is the structure of a typical repository...
/trunk
/tags
/tags/release1 (copied from trunk)
/tags/release1.1 (copied from branches/release1fixes)
/tags/release2 (copied from trunk)
/branches
/branches/release1fixes (copied from /tags/release1)
/branches/release2fixes (copied from /tags/release2)
In your case, where you want a personal, local tag of something under the
trunk, you might copy /trunk/scripts to /tags/chris/scriptsBeforeMyChanges.
How would that make other developers working on the trunk get a copy of
your tag?
--
Nikki Locke, Trumphurst Ltd. PC & Unix consultancy & programming
http://www.trumphurst.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Nov 24 22:29:43 2006