BK-FINDMERGE(1)

๐Ÿ“ฆ version 7.3.3, in alpine 3.24

๐Ÿ’– NAME ๐Ÿ’–

bk findmerge โ€” the glow-up command that shows you where two revisions were merged. This is from the BitKeeper Userโ€™s Manual, section (none) (yes bestie, thatโ€™s literally the section name ๐Ÿ’…).


โœจ SYNOPSIS โœจ

bk findmerge [โˆ’a] โˆ’rrev1 โˆ’rrev2 file

๐Ÿฆ‹ DESCRIPTION ๐Ÿฆ‹

Okay so picture this: bk findmerge prints the revision that is the least upper bound (LUB) of the two revisions you picked. Thatโ€™s the merge moment, the โ€œwhere did these two timelines collideโ€ revision.

If thereโ€™s more than one merge for those two revisions โ€” like when two different users merged them independently, no cap โ€” then bk findmerge returns the oldest one. Slay. And if you add the โˆ’a option, it lists all of them instead. Iconic behavior, honestly.


๐ŸŽ€ OPTIONS ๐ŸŽ€

  • โˆ’a โ€” lists all of the least upper bound merges where the two given revisions came together. All of them, bestie.
  • โˆ’rrev โ€” specifies the first and second rev. Both are required, fr fr.

๐Ÿท๏ธ CATEGORY

  • Utility

Big kisses from BitKeeper Inc, version 1E1 ๐Ÿซถโœจ and thatโ€™s the whole bk findmerge(none) footer vibe.

๐Ÿ“ฆ 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