CVS tags

[ziggy25]

Hi guys,

I use a tool called merant PVCS on a windows environment. I have recently
been doing some work on Unix's CVS and im struggling to find out how to
produce a revision report.

Using Merant PVCS, i was able to produce a report with all files that have a
specific tag. For example the output could look something like this if i ask
it to generate a report for all files that have the "Fault365" tag.

[code]

H:\services\pvcs.archives\src\N - ead\EDIREAD.C_v - Fault365 : 1.2
H:\services\pvcs.archives\src\N - ead\EDIREAD.H_v - Fault365 : 1.1
H:\services\pvcs.archives\src\N - end\edisend.c_v - Fault365 : 1.2

[/code]

It basicaly just produces a report that lists all the files that have the
Fault365 tag and shows the path to the file name and what version it
currently is at. I am trying to produce a similar report on cvs on Unix and
cant do it. Is it possible?

Thanks

[Cumps, Erik]

Post by ziggy25
Hi guys,
It basicaly just produces a report that lists all the files that have the
Fault365 tag and shows the path to the file name and what version it
currently is at. I am trying to produce a similar report on cvs on

Unix

Post by ziggy25
and cant do it. Is it possible?
Thanks

lstag is a tool that I've written for this purpose. It can show a list
of all
known tags for a module or all files and revisions tagged with a certain
tag.

I have attached the latest revision of lstag.

This version now allows listing of 'remote' modules. That is to say, you
are
no longer required to run lstag from within a checked out copy of the
module.

Usage #1, from within a sandbox:

$ lstag -l
to list all known tags

$ lstag this_is_a_tag
to list all files that are tagged with 'this_is_a_tag'

Usage #2, when not in a sandbox:

$ lstag [-d cvsroot] -l module
to list all known tags for module 'module'

$ lstag [-d cvsroot] this_is_a_tag module
to list all files in module 'module' that are tagged with
'this_is_a_tag'

If -d cvsroot is not specified the script will look in the CVSROOT
environment
variable. {Unless you are in a sandbox in which case the script will
take its
info from the CVS/ admin files)

Of course there is a difference in the file listing output when run from
within
a sandbox compared to when run outside. In the latter case lastag will
not be
able to present the file status for each file because there is no
sandbox.
Instead it claims the status is 'On-Server'.

As usual the code is tested but I am sure there are still bugs and
missing features
and whatnot... but lstag is still GPL so feel free to do with it as you
please.

HTH,
Erik