BK-CMDLOG(1)

💖 NAME 💖

okay so bestie, this is bk cmdlog — the BK-CMDLOG(1) page, straight outta the BitKeeper User’s Manual and sitting in the (none) section like it owns the place. 👑 It shows the log of commands executed in this repository. No cap, that’s the whole name-vibe. ✨

---

🌈 SYNOPSIS 🌈

bk cmdlog [−S] [−a] [−v] [−ccutoff] [pattern]
bk cmdlog [−r] [−ccutoff] [pattern]

two moods, same command, we love a flexible icon. 💅

---

🦋 DESCRIPTION 🦋

This lists the history of repository level commands that were run in the repository of the current directory. The repository level commands are bk clone, bk commit, bk export, bk pull, and bk push — those are the main characters. 📋

Commands are listed in least recent to most recent order, so oldest first, newest last. chronological slay. ⏳

---

💅 OPTIONS 💅

heads up: the synopsis has −S in it, but the OPTIONS section doesn’t give −S its own description. I’m not inventing one — we respect the lore. 🫡

• −S — appears in the synopsis, bestie; this page gives it no separate option blurb. 🙈
• −a — list history of all commands run in the repository, not just repository level commands. 🗂️
• −ccutoff — list commands which happened during the date range specified by cutoff. 📅
• −r — list command start and stops with relative times. This implies −a. ⏱️
• −v — each line of output is prefixed with userid, timestamp and BK version. Combined with the −a option, everything is listed, including commands run by BK itself. 🔍
• pattern — limit the output to lines matching (regexp) pattern. 🎯

---

⭐ EXIT STATUS ⭐

bk cmdlog returns exit status 0. that’s it, no plot twist. 💀✨

---

🎀 NOTES 🎀

The two command logs are maintained by BitKeeper in the BitKeeper/log directory. repo_log contains all repository level commands ever run in that repository. cmd_log contains recent commands run in that repository. 🗃️

Inside the cmd_log file, commands are logged at the time they start and at the time they finish. By default, cmdlog output is limited to the latter. Using the −av options, both the start and finish of commands is listed (as well as other events such as trigger launches). 🚀

The relative times displayed by the −r option are only printed if the bk version logged those times. Earlier versions of BitKeeper did not log this data so it will not appear in the output. 🕰️

When using the −r option, the relative time is in seconds and relative to the first user level command. For example, the start of a bk pull would be 0 seconds, all the subordinate logs will be relative to that. The final entry will represent the run time of the pull command. 🧮

---

💜 SEE ALSO 💜

• bk‐range — go read that one too, bestie. 💖

---

👑 CATEGORY 👑

• Repository — that’s the category, periodt. 🌟

---

footer tea, for the record: source BitKeeper Inc, version 1E1, and the date spot says bk cmdlog(none). bye bestie — go log something iconic! 🎀🦋💖