BK-CHECKSUM(1)

💖 bk checksum — BitKeeper User’s Manual 💖

Okay bestie, manual name folded in right at the top: this is the bk checksum page from the BitKeeper User’s Manual. Let’s get into it. ✨

🎀 NAME 🎀

bk checksum — check and/or fix BitKeeper per file checksums. That’s the whole assignment, no cap. 💅

🌸 SYNOPSIS 🌸

bk checksum [−s[offset]] [‐fv] [−rrev] [file ... | −]

🦋 DESCRIPTION 🦋

Okay so BitKeeper has more integrity checksums than the original SCCS had — and yes, SCCS had one over the whole s.file. BitKeeper keeps a checksum that’s compatible with SCCS, plus a whole new set of checksums, one per delta. This command is typically used to check and/or regenerate those per delta checksums. With no options at all, the default behavior is just to check each checksum and warn about any checksums that are missing or incorrect. 👑

This command may also be used to print a list of checksums of arbitrary data — see the −s option. 🌈

💀 WARNING 💀

Okay bestie, pay attention, because this is the serious one. The per delta checksums are part of the delta keys which are contained in the ChangeSet file. These keys are part of the metadata which BitKeeper uses to group deltas into changesets. If the checksums are changed, the checksums in the ChangeSet file must be correspondingly changed, and the process repeated for each copy of the repository.

Needless to say, we do not encourage the use of this command with the −f option unless you are very sure of what you are doing. 🚨

✨ OPTIONS ✨

• −f — fix any missing or incorrect checksums. 🛠️
• −rrev — limit checks to one revision. Faster than checking the whole file if the problem delta is known. ⚡
• −s[off] — generate and print the SCCS style 16 bit unsigned checksum starting at offset off. If off is 8, then this generates the same checksum as the per file checksum. If there are no file arguments, reads data from stdin (note: differs from other options which obey the normal BitKeeper file expansion rules). 📥
• −−safe−fix — only do fixes which do not alter the deltakey. The fix removes an unneeded merge parent. 🧚
• −v — be verbose. 🗣️

🔎 SEE ALSO 🔎

bk‐check — go peek at that one too, bestie. 🫶

⚠️ WARNINGS ⚠️

Do not depend on per file checksums being SCCS compatible — BitKeeper is likely to move to a CRC in a future release. 📉

📁 CATEGORY 📁

Admin. 🗂️

---

🫶 that’s the page, bestie — sign-off from BitKeeper Inc with footer bits 1E1 and bk checksum(none). The footer didn’t give a date, so no invented date, periodt. 💖