BK-KEYWORDS(1)

💖 NAME 💖

bk keywords — list of RCS and SCCS keywords.

That’s the whole NAME-section vibe, bestie. This is the page from the BitKeeper User’s Manual, and the header shows bk keywords(none) up top. It’s literally the keyword encyclopedia: SCCS keywords, RCS keywords, and the BitKeeper-only ones too. 💅

🦋 DESCRIPTION 🦋

BitKeeper supports both the standard SCCS keywords and most of the RCS keywords. On top of that, there are several keywords that are unique to BitKeeper. Slay.

Heads up: all of the revision-oriented keywords (e.g. %I%) are useless in BitKeeper, since they may change as a result of a re-synchronization that causes a branch creation. Use the %K% keyword when you need an identifier that is unique to a specific revision-level of a file. %K% is useful when tracking customer bugs. For example, a technician might ask the end-user to run the what command on an executable to check the versions of the components that make up a program. The person doing troubleshooting can then use the %K% keyword to track down the specific source files that make up the executable. 🔥

Another heads up: SCCS keyword expansion can cause problems in printf-like strings. To deal with unwanted keyword expansion, BitKeeper can be given options to expand only the first keyword found. See bk help admin.

---

💅 SCCS KEYWORDS 💅

Okay, here’s the full SCCS keyword lineup — every keyword and every example value, no skipping, no cap. ✨

• %A% — shorthand notation for an ID line with data for what(1). The expansion looks like:

%Z% %M% %I%%Z% @(#) GET 1.1@(#)

• %B% — SID branch component. Example value: 0.
• %D% — current date: yyyy/mm/dd. Example value: 1991/04/13.
• %E% — date the newest applied delta was created. Example value: 1991/04/13.
• %F% — SCCS s.file name. Example value: SCCS/s.GET.
• %G% — date the newest applied delta was created: mm/dd/yyyy. Example value: 4/13/1991.
• %H% — current date: mm/dd/yyyy. Example value: 4/13/1991.
• %I% — SID of the retrieved version: %R%.%L%.%B%.%S%. Example: 1.1 or 1.1.0.0 if fully specified as shown in the previous line.
• %K% — key for the delta (these do not change):

lm@va.bitkeeper.com|src/bkhelp.txt|19991116191217|50766

• %L% — SID level component. Example value: 1.
• %M% — module name: either the value of the m flag in the s.file, or the name of the s.file less the prefix.
• %P% — fully qualified s.file name. Example value: /u/lm/SCCS/s.GET.
• %R% — SID Release component. Example value: 1.
• %S% — SID Sequence component. Example value: 0.
• %T% — current time: hh:mm:ss. Example value: 12:41:29.
• %U% — time the newest applied delta was created: hh:mm:ss. Example value: 12:41:29.
• %W% — shorthand notation for an ID line with data for what. The expansion looks like:

%Z%%M% %I%     @(#)GET                  1.1

• %Y% — SCCS Compatible, not expanded in BitKeeper. So it just sits there, iconic but unexpanded. 🫶
• %Z% — 4-character string recognized by what. Example value: @(#).
• %@% — user@host.
• %#% — user.

---

🎀 RCS KEYWORDS 🎀

The following is the subset of RCS keywords that BitKeeper supports. The RCS keywords are only expanded if the RCS flag is turned on. See bk help admin. 🌸

• $Revision$ — expands like $Revision: 1.2 $.
• $Id$ — expands like $Id: s.rcs_expand.c 1.2 99/11/16 11:25:18‐08:00 lm@r.com $.
• $Author$ — expands like $Author: lm@r.com $.
• $Date$ — expands like $Date: 99/11/16 11:25:18‐08:00 $.
• $Header$ — expands like $Header: SCCS/s.rcs_expand.c 1.2 99/11/16 11:25:18‐08:00 lm@r.com $.
• $RCSfile$ — expands like $RCSfile: s.rcs_expand.c $.
• $Source$ — expands like $Source: /tmp/beta11/src/SCCS/s.rcs_expand.c $.

---

🔥 SEE ALSO 🔥

bk-admin, bk-config-etc, bk-get

🌈 CATEGORY 🌈

Overview

---

Footer tea, periodt: source BitKeeper Inc, version 1E1 — and the footer doesn’t show a date, so I’m not inventing one, bestie. Mystery date stays mysterious. 💅✨