BK-TAKEPATCH(1)

💅 BK-TAKEPATCH(1) 💅

okay so welcome to the bk takepatch page from the BitKeeper User’s Manual, bestie — this is the command that applies a BitKeeper patch, and it’s honestly giving “behind-the-scenes main character” energy. ✨

📛 NAME 📛

bk takepatch — apply a BitKeeper patch. periodt. 💖

✨ SYNOPSIS ✨

bk takepatch [−aciStv] [−ffile]

🦋 DESCRIPTION 🦋

The takepatch command is used to apply a BitKeeper patch. BitKeeper patches are how data is moved between BitKeeper repositories — like the group chat of repo data, no cap. 💅

Users do not normally invoke this command. It is called directly by bk pull, bk push, or bk receive, so it’s lowkey backstage crew, not the main event. 🎀

🔥 OPTIONS 🔥

• −a — apply the changes (call bk resolve.) ✅
• −c — do not accept conflicts with this patch. 🙅
• −ffile — take the patch from file and do not save it. 🍓
• −i — initial patch, create a new repository. 🎀
• −jN — unpack the patch using N parallel sub-processes. ⚡
• −−no−automerge — takepatch will try to automerge the file as part of taking the patch. This option will delay the merging until the resolve stage. bk pull −i uses this option. ⏳
• −S — save RESYNC and or PENDING directories even if errors. 💾
• −T — run in text only mode, do not use GUI tools. 📝
• −v — verbose level, more is more verbose, −vv is suggested. 🗣️

🌈 SEE ALSO 🌈

• bk‐pull
• bk‐push
• bk‐receive

👑 CATEGORY 👑

Repository — slay. 💅

shoutout to BitKeeper Inc for this page — the source/version/date-ish tag is 1E1, and it’s filed under bk takepatch(none). bye bestie! 🫶💖