On 3/6/07, Andy Levy <email@example.com> wrote:
> On 3/6/07, Emin.shopper Martinian.shopper <firstname.lastname@example.org> wrote:
> > For example, imagine I have a project with main/tags, main/branches, and
> > main/trunk. Every week I use svn copy to create a new entry in
> > main/tags/week-XXX-year-YYY. Now if someone does svn update on main,
> > may get hundreds of copies of things in main/tags taking up a lot of
> > space and network traffic.
> Why check out from /main in the first place? You can check out
> /main/trunk and /main/branches individually (or even individual
> branches, so that you don't have a copy of every branch locally), thus
> eliminating /main/tags from the update altogether.
> Only check out what you need.
Ideally, yes. But what if someone accidentally does an update of the root
More realistically, the script that does the svn copy to create the new tag
seems to cause a version of the newly copied "tag" to be instantiated in the
local file system. Is there a way to tell svn to make a copy so I can tag
something WITHOUT having a local version get checked out? Or whenever I want
to make a tag, do I need to do svn copy and then delete the result from the
Received on Tue Mar 6 20:05:35 2007