[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: question about tagging with cheap copies

From: Andy Levy <andy.levy_at_gmail.com>
Date: 2007-03-06 20:15:19 CET

On 3/6/07, Emin.shopper Martinian.shopper <emin.shopper@gmail.com> wrote:
> On 3/6/07, Andy Levy <andy.levy@gmail.com> wrote:
> > On 3/6/07, Emin.shopper Martinian.shopper <emin.shopper@gmail.com> 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,
> 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.
> Ideally, yes. But what if someone accidentally does an update of the root
> directory?

Again, you can't stop them without denying access to the directory
completely. Subversion does require some measure of user

> 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
> file system?

svn cp supports URL to URL copies. See svn help cp.

Short version: svn cp <SRC> <DEST> -m "Commit message"

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Mar 6 20:15:44 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.