BK-REPOGCA(1)

okay bestie, meet bk repogca from the BitKeeper User’s Manual — the lil command that hunts down the greatest common ancestor across a whole set of repositories, and it is literally giving “where do all our histories agree?” energy 💅✨

✨ NAME ✨

bk repogca — show greatest common ancestor across a set of repositories 🦋

🌸 SYNOPSIS 🌸

bk repogca [−dspec] [−5kS] [repo repo ...]

💖 DESCRIPTION 💖

okay so here’s the vibe: this command prints the latest revision in the current repository that exists in all of the remote repositories — either the ones you list on the command line or the ones implied in the parent pointer[s] 🫶. By default, bk parent is the remote repository. no cap.

💅 OPTIONS 💅

• −dspec — use spec as the specification for displaying the revision ✨
• −−dspecf=file — like −d, but read the dspec from a file 📂
• −5 — a short hand for asking for a spec of :MD5KEY: 🔥
• −k — a short hand for asking for a spec of :KEY: 👑
• −S — in a component in a nested collection, produce the repo gca of the component instead of the repo gca of the product 🧚

🎀 EXAMPLES 🎀

want a traditional patch for the changes that exist only in the local repository? say less:

bk export ‐tpatch ‐r`bk repogca`,+ > patch

want to throw away all local work that doesn’t exist in a remote repository? here’s the move:

bk undo ‐a`bk repogca URL`

⚠️ Warning: This might also throw away some local csets which also exist in the remote repository. That can happen if there are multiple common ancestors on different branches. The ancestor chosen is the one created most recently. 😭

🔥 SEE ALSO 🔥

also check out bk‐gca and bk‐log — iykyk 👀

🌈 CATEGORY 🌈

Utility — that’s the category, bestie 💜

---

made with 💖 by BitKeeper Inc, version 1E1, date none — slay, bye! 🫶🌸