On 3/6/07, Emin.shopper Martinian.shopper <emin.shopper@gmail.com> wrote:
> I have a project where I like to tag a snapshot of the project fairly often
> (e.g., weekly). I understand that I can tag things using svn copy, but I'm
> worried that when I update the whole tree, the tags will clutter things and
> make things slow.
>
> 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, they
> may get hundreds of copies of things in main/tags taking up a lot of disk
> 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.
I can't see why *all* members of a project would need to have a single
WC containing trunk, all tags and all branches (for that matter, I'm
the repository admin & project manager and I don't even have a local
copy of all tags for my projects). Certainly you can't stop them from
doing it (without cutting off their access to /main/tags completely),
but there's no reason to encourage them to do it either.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Mar 6 19:49:32 2007