BK-UNPULL(1)
π NAME π
okay so bestie, this is bk unpull from the BitKeeper Userβs Manual β manual name bk unpull(none) β and its whole vibe is undoing the changesets that got added by bk pull. iconic cleanup energy, no cap. π§Ήβ¨
πΈ SYNOPSIS πΈ
bk unpull [βfqSs]
π¦ DESCRIPTION π¦
bk unpull removes the changesets that were added by the most recent bk pull command. literally the undo button for that pull, but make it Unix. ππ
If youβve committed a local changeset, bk unpull can not be executed until that changeset is removed by bk undo. so yeah: local commit? handle it with bk undo first, bestie. π«Ά
π NOTE π
bk unpull will discard the merge changeset, if any β in this context that merge is not considered part of the local work. π If the merge was complicated, it is advisable to save a patch. consider this your gentle βsave first, panic laterβ moment. π
β¨ OPTIONS β¨
βfβ Force unpull. force it, bestie, with feeling. π₯βqβ Quiet mode. shhh, minimal output vibes. π€«βsβ Do not save a backup patch inBitKeeper/tmp/unpull.patch. no backup patch, no extra file, just vibes. π
π SEE ALSO π
bkβpullbkβundo
π CATEGORY π
- Common
- Repository
π«Ά sign-off time: source/version is BitKeeper Inc, version1E1. The date slot in this footer is not listed, so thereβs no date to report, bestie. Manual name:bk unpull(none). π
π¦ 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