BK-ADMIN(1)

🎀 NAME 🎀

okay so this is bk admin(none) from the BitKeeper User’s Manual — the iconic page for administering BitKeeper files. Yes bestie, it’s giving “one command that does literally everything” energy, and we’re gonna get into all of it 💅

✨ SYNOPSIS ✨

bk admin options [file ... | −]

💖 DESCRIPTION 💖

The bk admin command is used to administer BitKeeper files. There are options for changing per file features, modifying file metadata, verifying file checksum and metadata, changing the file compression mode, and/or recalculating the file checksum. So yeah — it’s a whole toolbox in one little command, no cap 🧰✨

💅 OPTIONS 💅

• −C[id] — set or remove the changeset file string in the 1.0 delta (very rarely used, not recommended). The string is used to associate the file with a particular repository idea and usually the same as the output of bk id.
• −D — remove the delta changeset marks (rarely used—not recommended).
• −fflag — set a per file flag. Many of the flags may be set automatically upon file creation by adding an entry to the BitKeeper/etc/config file. See bk help config‐etc for information on how to do so. The possible values for flag are:
  • BITKEEPER — mark the file as a BitKeeper file (very rarely used, not recommended)
  • EOLN_NATIVE — use the operating system’s native end-of-line termination (i.e., \r\n on Windows and \n on all other platforms.) EOLN_NATIVE is set to “on” by default.
  • EOLN_UNIX — use the UNIX end-of-line termination (i.e., \n) on all platforms.
  • EOLN_WINDOWS — use the Windows end-of-line termination (i.e., \r\n) on all platforms.
  • EXPAND1 — expand keywords in first line that contains keywords only (printf conflicts) (May be set in BitKeeper/etc/config).
  • NOMERGE — do not attempt to automerge this file; treat it as if it were a binary file and always force a choice between the local and remote versions of the file.
  • RCS — expand RCS keywords, i.e., $keyword$ etc. (May be set in BitKeeper/etc/config).
  • SCCS — expand SCCS keywords, i.e., %K% etc. (Setting this in BitKeeper/etc/config applies this behavior to all subsequently created files; it does not affect existing files! You must use bk admin to explicitly on existing files.)
• −Fflag — delete the flag flag, reverting to default behavior.
• −h — check s.file structure in general, but limited to ATT SCCS features.
• −hh — as above, but also check BitKeeper specific (in addition to ATT SCCS) features.
• −hhh — as above, but also check time stamps.
• −i[file] — read initial text from file (default stdin).
• −q — run quietly.
• −ycomment — make comment be the checkin comment for the initial checkin (only valid with −i).
• −z — recalculate file checksum.
• −Zalg — compress stored s.file with alg. Compression is on by default because the space savings are substantial and there is little or no performance difference. The default may be set in BitKeeper/etc/config. alg may be:
  • gzip — like gzip(1)
  • none — no compression

😭 BUGS 😭

ngl, this command does way too much and is likely to be split apart. Do not depend on these options for scripts. Fr fr, that’s a warning bestie — scripts should not be leaning on this chaotic energy 💀

🔎 SEE ALSO 🔎

bk‐check, bk‐checksum, bk‐chmod, bk‐delta, bk‐cset, bk‐get, bk‐id, bk‐new, bk‐log, bk‐keywords, bk‐config‐etc

👑 CATEGORY 👑

Admin

xoxo bestie 💖 source/version: BitKeeper Inc, 1E1; date: none; page: bk admin(none). go forth and administer those files ✨