BK-REMERGE(1)
π 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 marker1E1, and the footerβs right-hand title isbk 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
- Copyright (c) 1998-2015 BitKeeper Inc
- Copyright (C) 1989, 1990, 1991, 1992, 2001, 2002, 2003, 2004, 2005 Free Software Foundation, Inc
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms