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

Getting list of tags/branches

From: Walt Armour <WaltA_at_concur.com>
Date: 2004-09-09 20:17:48 CEST

(As an aside, the list archive appears to not search any recent posts. I
can browse everything but the search isn't giving me anything more recent
than 2003.)

I'm aware that svn does not store tag/branch info like cvs. This makes it
more difficult to find a list of tags/branches for a specific file. I'm
looking for some solution that will help in this regard.

The real problem that I'm trying to solve is this: I cannot be guaranteed of
the exact spelling of any particular tag (some people abbreviate different
things in different ways). However, I know generally what a tag name should
be and if I see it then I will recognize the tag that I need (people
occasionally leave out an underscore or accidentally use a dash instead).
At the moment svn seems to make this simple task quite difficult/expensive.

The approach I'm looking for would just give a list of tags/branches,
period. My thought was to use 'svnlook tree' but on out repository it is
hideously slow (mainly because it is a massive amount of output). However,
if I could restrict the depth of the tree that is produced it may run quite
a bit faster and the resultant output would be more usable for this
particular purpose. Perhaps something like 'svnlook tree --depth 1
/my/repo/path /branches'.

What is the feasibility of adding this type of '--depth' argument to
'svnlook tree'? Are there other approaches that might give me what I want
(I am even considering a cron job with some parsing to provide me a daily
list like this)?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Sep 9 20:16:59 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.