[fpc-pascal] How to discover which files are tagged or branced in a hook script?

Bo Berglund bo.berglund at gmail.com
Sat Dec 16 14:24:46 CET 2017

On Sat, 16 Dec 2017 00:27:27 +0100, Bo Berglund
<bo.berglund at gmail.com> wrote:

>If there is a commit to a tag operation, how can I find out which is
>the tag and which files carry that tag?

I have tried various way to get at the information but failed so far,
the best I could do is  to use 
svnlook changed -r <revision> <repository>
but then I have to parse the returned path looking for keyword /tags/
and grab the bit following this keyword:

D:\>C:\Programs\Subversion\svnlook changed -r 792 D:\SVN\bosse
A   XMLTV/tags/Rel_XMLTV2MEI_1-0-2-56_2011-02-09/

If I use "info" I am getting the response below but than the tag name
is embedded in the log message and cannot be relied upon:

D:\>C:\Programs\Subversion\svnlook info -r 792 D:\SVN\bosse
2011-07-05 09:10:25 +0200 (ti, 05 jul 2011)
This commit was manufactured by cvs2svn to create tag

And using "changed" is basically also non-working except for parsing a
supplied path:

D:\>C:\Programs\Subversion\svnlook changed -r 792 D:\SVN\bosse
A + XMLTV/tags/Rel_XMLTV2MEI_1-0-2-56_2011-02-09/
    (from XMLTV/trunk/:r791)

And none of these show the *files* affected by the tagging....

So I tried to use the following command:

D:\>C:\Programs\Subversion\svnlook tree -r 792 D:\SVN\bosse --show-ids

But this lists ALL files in the *whole* repository, not even limiting
to the files in the module that was tagged by r792 even though the
documentation shows otherwise.

The repository is organized into modules (top level directories) as
was the CVS repository. These are each containing a separate project
non-related to the other projects except for the department managing
those projects.

When the whole *project* is tagged I want to be able to list all the
involved files even though they are not modified themselves.

How can this be accomplished? svnlook seems not to be able to do it...

Bo Berglund
Developer in Sweden

More information about the fpc-pascal mailing list