BK-HISTORY(1)

🌸 NAME 🌸

okay bestie, welcome to bk history — manual name bk history(none), straight from the BitKeeper User’s Manual 💅. This page is literally your guide to viewing changes to files and/or repositories ✨. It’s giving “history tour” but make it Unix, and yes, it ate — no cap.

---

💖 TEXTUAL HISTORY 💖

There are multiple tools to view the history of the repository, of a file, or of a collection of files such as a directory. All the tools are described more completely on their own man pages — go read those too, bestie 🫶.

Want the high-level changes to a repository? Type:

$ bk changes

bk changes has many options to control which changesets are shown, how they are shown, etc. It is the primary way for finding out what happened in the repository, and reading the changes man page is highly recommended, fr fr — slay.

The revision history of a file can be accessed by typing:

$ bk log foo.c

bk log has many options. The most commonly used is the −r option, which is used to select a particular revision of the file. For example, to see the most recent check-in for every file in the current directory:

$ bk log −r+

The bk log command documents the metadata associated with a BitKeeper file as well as how to display it. Reading the bk log man page is highly recommended — seriously, it’s highkey iconic 🌟.

The bk sccslog command is a time ordered view of changes over a set of files. Unlike bk log, bk sccslog sorts all changes from all of the specified (or implied) files and then displays each change in chronological order. The following will display the changes which have happened to all the files in the current directory:

$ bk sccslog

All three commands support the same range notation as well as a method of controlling the output format known as “dspecs”, which are documented on the bk log man page 🎀. Not me being obsessed with dspecs, but here we are.

---

🦋 GRAPHICAL HISTORY 🦋

There are two graphical tools which are primarily used to view changes to files or repositories. These tools are described more completely on their man pages — the full lore is lowkey there, iykyk 😌.

bk csettool is a graphical changeset viewer which displays the list of changes in each changeset, the ChangeSet history, and the file differences (in a side by side display) for each file in each changeset. It is the graphical version of bk changes. Obsessed 💖.

bk revtool is a tool which shows the revision history graph of either a specified file or of the ChangeSet file. Nodes in the graph may be selected to view that version of the file. If two nodes are selected then the differences between the two versions are shown. Vibe check: main character graph energy, periodt ✨.

---

🔥 SEE ALSO 🔥

• bk‐changes
• bk‐csettool
• bk‐difftool
• bk‐log
• bk‐range
• bk‐revtool
• bk‐sccslog
• bk‐set

---

👑 CATEGORY 👑

• Overview
• Repository

---

💖 cute sign-off: source/version BitKeeper Inc, 1E1, footer/date bk history(none) — mwah, bestie! 🌈