Hi,
We use an automated
build tool that performs many builds each day. Each time there is a successful
build it applies an appropriate tag to our CVS repository. This has been running
for a number of months now and on many files there are well over 100 tags - for
files that don't change
There's a small incremental cost per tag per file: Each tag is represented
by a line in each RCS file. This is typically less than 100 bytes but
it depends on the length of the tag and the depth of the branch to which the
tag is applied. In terms of time, this amounts to probably a few
In addition to tagging, we also built a manifest of the source files,
checked it in, and applied the same tag as was applied to the rest of the
build. The manifest was stored separately from the source code so that
developers wouldn't muck with its tags. Our rebuild procedure used that
file to
