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

Re: tagging just a few files

From: Sunil Shetye <shetye_at_bombay.retortsoft.com>
Date: 2004-11-26 11:42:32 CET

Quoting from Benjamin Pflugmann's mail on Thu, Nov 25, 2004 at 10:33:27PM +0100:
> You can prepare a working copy to represent what you want to be tagged
> and then tag the working copy. That should handle both cases, a) and
> b) fine. Would that work for you?


> Done. You can either throught the working copy away or get back a full
> working copy by svn update. If you repeat the same procedure in order
> to tag REPOS/tags/pkg1-v101, then
> svn diff $REPOS/tags/pkg1-v100 $REPOS/tags/pkg1-v101
> should do what you expect (so long as I understood correctly what you
> expect).

Yes, you have understood my problem correctly. If you do look at
Method 3 in my original mail,


it is similar to the method you have described. The only difference is
that it does a "svn copy" first and then "svn rm" on the tag
directory. And my original question was:

Is it possible to have an option like "--parents" to "svn copy" to
make tagging of some files easier?

Why should I do tagging in a roundabout way when this one option is
going to solve all my problems. With your solution, per package, I
will have to:

1) checkout the repository,
2) figure out what files and directories to remove,
3) remove them,
4) tag the remaining.

This obviously is a sub-optimal (and idiotic, IMO) way of tagging
files. Not to mention, network-intensive. And error-prone, if I don't
figure it out right!

> Of course, splitting up the packages in pkg1, pkg2 and pkg-common
> might be the better long-term solution.

Each individual package is meant to be compiled independently.

Sunil Shetye.
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Nov 26 11:36:15 2004

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.