<commit_before>.so bk-macros
.TH "bk tag" 1 20%E% "\*(BC" "\*(UM"
.\"    ====================== BitKeeper tags ======================
.SH NAME
bk tag \- tag the \*(BK repository with a symbolic name
.SH SYNOPSIS
.Bc bk tag [
.OPTreq \-r rev
.B ] 
.ARG symbol
.SH DESCRIPTION
.LP
Symbols (aka tags) are used when you want to record the state of a tree.
It is quite common to ``tag the tree'' with a release name when shipping
a product to customers.  
.LP
To add a tag to the repository, make sure that you've checked everything
in and created a changeset.  You can use bk status to see what needs to
be checked in and/or committed to a changeset. Tag the tree by typing:
.DS
$ bk tag Alpha
.DE
The Alpha symbol will be set on the most recent changeset.  Or you
can commit a changeset and tag the tree at the same time with the \-S
option to commit:
.DS
$ bk commit \-SAlpha
.DE
If you want to recover the state of the world as of a tag, do this:
.DS
$ bk clone \-rAlpha source_repository Alpha
.DE
which will create a repository which has everything up to and including
the Alpha changeset.
.LP
If you discover that you should have tagged a changeset after more
changesets have been added to the repository, use the 
.B \-r 
option to
select the proper changeset.  You can find out which revision to tag
by running 
.BR bk\ changes .
.LP
A frequent problem is that you tag a changeset with "Done" and then
discover you aren't done.  You may update the tag to the later changeset
by running the 
.DS
$ bk tag Done 
.DE
command again.  If there are multiple tags
with the same name, \*(BK takes the most recently applied tag (which
means you can move a tag backwards by specifying an older revision of
the cset file).
.LP
Tagging individual files, while possible with the admin command, is
generally unnecessary.  However, if you want to tag all the files,
you can do so like this:
.DS
$ bk \-r admin \-SAlpha
.DE
That will put the Alpha tag on top of trunk on all files.
.SH BUGS
.LP
Need a way of setting a tag in citool.
.SH "SEE ALSO"
.SA admin 1
.SA changes 1
.SA commit 1
.SA prs 1
.SH CATEGORY
.B Repository<commit_msg>make tag man page come up when searching for "label" as requested by lee. Symbols (aka tags) --> Symbols (aka tags or labels).<commit_after>.so bk-macros
.TH "bk tag" 1 20%E% "\*(BC" "\*(UM"
.\"    ====================== BitKeeper tags ======================
.SH NAME
bk tag \- tag the \*(BK repository with a symbolic name
.SH SYNOPSIS
.Bc bk tag [
.OPTreq \-r rev
.B ] 
.ARG symbol
.SH DESCRIPTION
.LP
Symbols (aka tags or labels) are used when you want to record the state of 
a tree.  It is quite common to ``tag the tree'' with a release name when 
shipping a product to customers.  
.LP
To add a tag to the repository, make sure that you've checked everything
in and created a changeset.  You can use bk status to see what needs to
be checked in and/or committed to a changeset. Tag the tree by typing:
.DS
$ bk tag Alpha
.DE
The Alpha symbol will be set on the most recent changeset.  Or you
can commit a changeset and tag the tree at the same time with the \-S
option to commit:
.DS
$ bk commit \-SAlpha
.DE
If you want to recover the state of the world as of a tag, do this:
.DS
$ bk clone \-rAlpha source_repository Alpha
.DE
which will create a repository which has everything up to and including
the Alpha changeset.
.LP
If you discover that you should have tagged a changeset after more
changesets have been added to the repository, use the 
.B \-r 
option to
select the proper changeset.  You can find out which revision to tag
by running 
.BR bk\ changes .
.LP
A frequent problem is that you tag a changeset with "Done" and then
discover you aren't done.  You may update the tag to the later changeset
by running the 
.DS
$ bk tag Done 
.DE
command again.  If there are multiple tags
with the same name, \*(BK takes the most recently applied tag (which
means you can move a tag backwards by specifying an older revision of
the cset file).
.LP
Tagging individual files, while possible with the admin command, is
generally unnecessary.  However, if you want to tag all the files,
you can do so like this:
.DS
$ bk \-r admin \-SAlpha
.DE
That will put the Alpha tag on top of trunk on all files.
.SH BUGS
.LP
Need a way of setting a tag in citool.
.SH "SEE ALSO"
.SA admin 1
.SA changes 1
.SA commit 1
.SA prs 1
.\" help://tags
.\" help://label
.\" help://labels
.SH CATEGORY
.B Repository
{'fraction_non_alphanumeric': 0.08384180790960452, 'fraction_numerical': 0.0031638418079096044, 'mean_word_length': 3.3477406679764243, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 4, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6492950', 'n_tokens_mistral': 1391, 'n_tokens_neox': 1315, 'n_words': 789}