BK-PARENT(1)

💅 bk parent — manage repository parent pointer[s] 💅

BitKeeper User’s Manual, section none — okay so that’s the manual name folded in right at the top, bestie. ✨

🌸 NAME 🌸

bk parent — manage repository parent pointer[s]. Yes, plural pointer[s], we contain multitudes. 💖

✨ SYNOPSIS ✨

bk parent [−a|−r|−s] [−1iloq] [repository] [repository]

Like, there are moods for this command:

🎀 SETTING PARENT POINTERS 🎀

bk parent −s [−ioq] repository [repository]

🫶 ADDING PARENT POINTERS 🫶

bk parent −a [−ioq] repository [repository]

💔 REMOVING PARENT POINTERS 💔

bk parent −r [−ioq] repository [repository]

🦋 LISTING PARENT POINTERS 🦋

bk parent [−1iloq]

🦋 DESCRIPTION 🦋

Okay so bk parent is the command that lets you set, add, adjust, remove, or list parent pointers for a repository. A parent pointer is a BitKeeper URL — it’s the location from or to which a repository gets or sends updates when running bk pull or bk push. The typical case is that a repository has only one “parent,” but it is possible for a repository to have multiple parent pointers, and each pointer may be incoming, outgoing, or both. Lowkey flexible, highkey iconic. 💅

When setting the parent pointer, the parent command is backwards compatible with earlier versions if and only if there is currently no parent pointer or there is one and only one push/pull parent pointer. No cap.

The parent is automatically set when a repository is cloned and will be named according to the access method — see bk help url for more information. Automatic and method-named, we love a self-sufficient icon. 🎀

💅 OPTIONS 💅

• −1 — List only the first parent found. May be combined with −i or −o to list the first incoming or outgoing parent pointer[s] respectively. First one only, main character energy.
• −a — Add the specified parent pointer to the list of parents. May be combined with −i or −o to add just the incoming or outgoing parent pointer[s] respectively. Adding to the group chat, but for repo pointers.
• −i — Operate only on incoming (pull) parent pointers. May be used when setting, adding, adjusting, removing, or listing parents. Incoming only, bestie.
• −l — List the parent pointer[s] without any annotations, one per line. May be combined with −i or −o to list just the incoming or outgoing parents respectively. Clean list, no extra commentary, one per line.
• −o — Operate only on outgoing (push) parent pointers. May be used when setting, adding, adjusting, removing, or listing parents. Outgoing only, slay.
• −q — Do not produce output when adding/removing/listing parents. May be combined with −i or −o to query whether the repository has an incoming (pull) or outgoing (push) parent pointer, exit status will be 0 if any matching parent pointers where found, otherwise exit status is 1. Quiet mode: the vibes are silent, the exit status speaks.
• −r — Remove the parent pointer. May be combined with −i or −o to remove just the incoming or outgoing parent pointer[s] respectively. Using −i or −o on a bidirectional parent pointer converts the parent pointer to unidirectional. It’s giving “breakup, but make it directional.”
• −s — Set the parent pointer[s] to the specified list, replacing any existing pointers. This option is always required to override any existing parent pointers except in the case that there is only one bidirectional parent pointer and it is being replaced with one bidirectional parent pointer (backwards compat). Big “replace the whole vibe” energy.

😭 BUGS 😭

The term parent is somewhat of a misnomer in a peer to peer system. Since it is quite common to use BitKeeper repositories in a parent/child relationship most of the time, we have stuck with the term. Ngl, the terminology ate, even if it’s not technically perfect.

👑 SEE ALSO 👑

• bk‐bkd
• bk‐changes
• bk‐clone
• bk‐pull
• bk‐push
• bk‐url

Go read these next, bestie. 🫶

🌈 CATEGORY 🌈

Repository. That’s the category, periodt.

---

Cute sign-off: BitKeeper Inc made this, the date/version slot says 1E1, and the footer title is bk parent(none) — that’s the whole footer, and I’m obsessed. 💖💅🫶