How to find out which CVS tags cover which files and paths

cvs

There is a legacy CVS repository, which contains a large number of directories, sub-directories, and paths. There is also a large number of branches and tags that do not necessarilly cover all paths & files – usually a subset. How can I find out, which branch / tag covers, which files and paths?

CVS log already provides the list of tags per file. The task requires me to transpose this into files per tag. I could not find such functionality in current WinCVS (CVSNT) implementation. Given ample empty cycles I can write a Perl script that would do that, the algorithm is not complex, but it needs to be done.

I would imagine there are some people who needed such information and solved this problem. Thus, I think should be a readily available (open source / free) tool for this.

Best Answer

To list tags on a file one can also do:

cvs status -v <file>

Related Solutions

CVS: List all files changed between tags (or dates)

I suppose this command would help:

cvs diff -N -c -r RELEASE_1_0 -r RELEASE_1_1 > diffs

where RELEASE_1_0 and RELEASE_1_1 are the names of your tags.

You can find a little more information on cvs diff command here

plus it should be fairly simple to create a script to make report more suitbable for your needs, ex: number of files changed, created deleted etc. As far as I know the most common cvs GUI tools (wincvs and tortoise) do not provide something like this out of the box.

Hope it helps ;)

Tagging part of a repository in subversion

I don't know if this is the "correct" answer, but I can think of two options.

A. Tag and delete:

Tag your /project/libs directory as project-release-1;
Delete "test" and "mock" directories from project-release-1. Alternatively, first create a project-release-1-with-tests tag with everything, then tag (copy) that directory as project-release-1 and repeat #2 above.

B. Use "externals":

Create an empty project-release-1 directory under tags. Don't really tag, just create the directory.
Edit the properties of that directory, add a property named "svn:externals". In that property's value enter: lib1 -r $REV url:to/project/libs/lib1 lib2 -r $REV url:to/project/libs/lib2

where $REV is the revision number of the tagged source code. Later when you'll check out the "without tests" directory you'll get the two "tagged" directories.

I believe the first option is better, as tools that analyze branches and tags will have a better change of understanding what you did.

On a side note, I wonder why you'd want the test-less tag; Why does it bother you that you have the tests in the tag?

Noam.

Best Answer

Related Solutions

CVS: List all files changed between tags (or dates)

Tagging part of a repository in subversion

Related Topic