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

Re: Viewing the labels that are attached to a certain file

From: <kfogel_at_collab.net>
Date: 2004-12-10 19:43:49 CET

Matthias Bauer <bauer@four-d.de> writes:
> I am in the process of evaluating Subversion for using it as the primary
> version repository in our company. We are currently using an RCS based
> repository with the commercial frontend tool CS-RCS. I am also familiar with
> the concepts of CVS and Clearcase.
> Subversion looks good so far, even though it needs some time to get used to
> the concept of implementing tags/labels and branches with the concept of
> "cheap copies". I know this issue has already been discussed a lot on this
> list and I don't want to restart these discussions. However, there is one
> thing I bitterly miss, when implementing tags/labels with copies of trees or
> files in Subversion: How can I find out, which tags/labels are attached to a
> file?
> Lets look at an example:
> - There is a file test.txt that is located in root:/trunk.
> - I am tagging different versions of this file by copying it to
> root:/tags/int_001, root:/tags/int_002, root:/tags/int_003, ...
> - Now I want to have a chance to look at test.txt and easily find out, which
> tags/labels are attached to this file. CVS offers a command for this.
> Is there a Subversion command that allows to extract the information for
> this?

No, but we agree this is a serious lack and someday (don't ask me
when, we've got a lot of enhancement requests in the queue :-) !) it
will be remedied.

In the meantime there are workarounds. You can write a script to do
'svn ls' in the appropriate tags. I realize this is not ideal, but it
should work.

Good luck,

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Dec 10 19:45: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.