BK-REMERGE(1)

πŸ“¦ version 7.3.3, in alpine 3.24

πŸ’– NAME πŸ’–

Manual name: bk remerge(none) β€” from the BitKeeper User’s Manual. The name/description combo is literally bk remerge βˆ’ redo the last merge, and that’s the whole main character energy of this page. Bestie, it’s here to help you redo the last merge. πŸ’…

✨ SYNOPSIS ✨

bk remerge [βˆ’T] file [file ...]

πŸ’… DESCRIPTION πŸ’…

Okay so bk remerge looks at the specified file[s] and tries to remerge the last merge. No cap, that’s the vibe.

Each file may not be edited with modifications and must have a merge as the most recent delta; files not meeting these requirements are skipped. So if your file doesn’t match, it gets skipped β€” don’t take it personally. 🫢

The merged file is left as the current working file after the merge is completed. The merge may be graphical (default) or text based. In the latter case, the marked up file is left as the working file and you must manually edit it to complete the merge. That’s the text-based path: marked up file stays put, and you’re on manual-edit duty, bestie. 😭

πŸŽ€ OPTIONS πŸŽ€

  • βˆ’T β€” use a text based merge tool. That’s the icon, the moment, the whole flag. ✨

πŸ¦‹ SEE ALSO πŸ¦‹

Go say hi to bk‐fm3tool and bk‐smerge β€” iykyk, they’re in the same little Unix friend group. πŸ¦‹

🌈 CATEGORY 🌈

File β€” that’s the category, periodt. πŸ‘‘

Cute sign-off: source is BitKeeper Inc, version/date marker 1E1, and the footer’s right-hand title is bk remerge(none) β€” bye bestie, go remerge that last merge πŸ’–πŸ’…
πŸ“¦ 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