BK-GCA(1)

πŸ“¦ version 7.3.3, in alpine 3.24

πŸ’– NAME πŸ’–

bk gca β€” show the greatest common ancestor. This one hangs out in the none manual section, and yes that’s literally the section name bestie πŸ’…

🌸 SYNOPSIS 🌸

bk gca βˆ’rrev1 βˆ’rrev2 file

✨ DESCRIPTION ✨

okay so bk gca prints the revision that is the greatest common ancestor (GCA) of the two revisions you specify. That’s the whole move 🫢

But plot twist: if there is no node in the graph that’s an exact match, the printed revision will have an include list and/or an exclude list of revisions. Those revisions must be added to the revision in order to get the actual GCA. No cap, this caveat is important. πŸ’€

πŸŽ€ OPTIONS πŸŽ€

  • βˆ’rrev β€” specify the first and second rev (both are required). Like, both of them, fr fr β€” you cannot just pick one and call it a day πŸ™ˆ

πŸ¦‹ CATEGORY πŸ¦‹

Utility β€” a cute little utility category, iconic behavior.


Cute sign-off: shoutout to BitKeeper Inc for the source credit, the footer’s 1E1 version/date bit, and the bk gca(none) tag still doing its thing at the end. Byeee βœ¨πŸ’–

πŸ“¦ where this page comes from
  • alpine 3.24: bitkeeper-doc 7.3.3-r1 Β· Apache-2.0
  • πŸ’– girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms