<html><head><title>VCP::Filter::addlabels - Add labels to each revision</title></head><body><h1><a name="NAME">NAME
</a></h1><p>VCP::Filter::addlabels - Add labels to each revision
<p><hr><h1><a name="SYNOPSIS">SYNOPSIS
</a></h1><pre> ## From the command line:
vcp <source> addlabels: "rev_$rev_id" "change_$change_id" -- <dest>
</pre><pre> ## In a .vcp file:
</pre><pre> AddLabels:
rev_$rev_id
change_$change_id
# ... etc ...
</pre><p><hr><h1><a name="DESCRIPTION">DESCRIPTION
</a></h1><p>Used when you want to track the original rev_id, change_id, branch_id,
etc. each revision had in the source repository by adding a label.
Can be used to turn any piece of metadata in to a label.
<p>Note that the fields
<pre> source_name, source_filebranch_id, source_branch_id,
source_rev_id, source_change_id
</pre><p>are set by VCP to be the same value as the corresponding fields
without the source prefix (except source_filebranch_id, which is built
from the file name, rooted in the repository, and for cvs
repositories, the branch number in angle brackets.) These source_*
fields (intended to be immutable in vcp) should be used to make labels
rather than their mutable equivalents which may be changed via a vcp
filter.
<p>There is no way to add labels only to selected revisions at this
time, but if you try to add a label for metadata that is undefined
or empty, it will not be added.
<p><hr><h1><a name="AUTHOR">AUTHOR
</a></h1><p>Barrie Slaymaker <barries@slaysys.com>
<p><hr><h1><a name="COPYRIGHT">COPYRIGHT
</a></h1><p>Copyright (c) 2000, 2001, 2002 Perforce Software, Inc.
All rights reserved.
<p>See <a>VCP::License</a> (<code>vcp help license</code>) for the terms of use.
<p><hr><i><font size="-1">Last updated: Fri Jun 4 14:21:30 2004</font></i></body></html>