BK-CLONE(1)

💖 bk clone — BitKeeper User’s Manual 💖

section (none), bestie — yes, that’s the manual-name situation. This page is for bk clone, and it’s giving “copy the whole package” energy with full repo-brain. 🫶

✨ NAME ✨

bk clone — create a new copy of a package. That’s the mission statement, periodt. 💅

🌸 SYNOPSIS 🌸

bk clone [-q] [-rrev] [more opts] from [to]

🦋 DESCRIPTION 🦋

okay so clone copies from the from repository and creates a copy at to. If to is not specified, then the basename of from is the implied destination. Cute, efficient, no notes. 💖

This works for fully and partially specified pathnames as well as BitKeeper URLs. See bk help url for further naming information. iykyk. 🌈

If bam_url is specified, it tells the destination repository what to use as a BAM server. Normally a new repository inherits the BAM server URL from the source repository. This argument is required when cloning a BAM server to a BKD. required, not optional, bestie. 🔥

If rev is specified, the cloned repository will include only changesets up to and including rev. Slay, partial clone. ⭐

The cloned repository remembers from which repository it was cloned. The from repository is known as the “parent,” while the newly cloned repository is known as the “child.” family tree behavior, honestly. 👑

Subsequent updates to the child can be done by running bk pull. Changes made in the child can be pushed back into the parent by running bk push. main character repo energy fr fr.

🎀 NOTE 🎀

Only completed changesets are cloned. Any pending deltas are removed from the child before the clone completes. no half-finished vibes allowed. 💀

On recent (2014) versions of Ubuntu (and other Linux distributions), the use of hardlinks has been curtailed for security reasons. clone will fall back to using copies, see http://man7.org/linux/man-pages/man5/proc.5.html and search for protected_hardlinks. Using copies instead of links is slower and takes more disk space so you may want to disable this security feature if all of your users are trusted. 🫶

💅 OPTIONS 💅

• -@base_url — Use a local repository as a baseline for the clone so that only the changes need to be transferred from a remote location. big “don’t resend the whole thing” energy. ✨
• -Burl — Set the BAM server url to url in the destination repository.
• --checkout=mode — Override any previous setting for the checkout mode. Valid values for mode are none, get, or edit. Note that this mode becomes "sticky" in that the checkout mode will be added to bk root/BitKeeper/log/config. If no other config overrides that, then this mode will "stick" for subsequent updates. sticky config, but make it fashion. 🍓
• --downgrade — By default, new clones will use the same storage format as the repository being cloned. This option forces the new clone to use the older, backwards compatible format (at the cost of lower performance). older format, lower performance, but backwards compatible. periodt.
• -Eenv=val — Export an environment variable to the bkd running in the remote BitKeeper repository. Typically used to pass information to remote triggers. Only variables with the prefix BKU_ are allowed. no random env vars, bestie. 🙈
• -jjobs — Set the level of parallelism for the unpacking and checking out of files. get those jobs going. ⭐
• --no-hardlinks — Clone normally uses hard links whenever it can. This option will prevent this and is useful to create an archive of a repository that copies every file. archive girlies rise. 🎀
• --parents — Instead of setting the parent to the from url, use from’s parents. Useful when you want to pull from/push to the same places as from. inherited parent drama, but useful. 💜
• -q — Run quietly. shhh. 🤫
• -rrev — Clone the repository up to and including cset rev. A changeset number or changeset key can be used to specify rev. See bk help terms for more information. cset language, got it. 🌈
• --upgrade — By default, new clones will use the same storage format as the repository being cloned. This option forces the new clone to upgrade to the latest storage format. In bk-6.0, the storage format was changed to support higher performance. newer format, higher performance, slay. 🔥

🌟 SEE ALSO 🌟

• bk-alias
• bk-bam
• bk-bkd
• bk-parent
• bk-pull
• bk-push
• bk-relink
• bk-terms
• bk-triggers
• bk-url

👑 CATEGORY 👑

• Common
• Repository

source: BitKeeper Inc · version: 1E1 · date: not listed in the footer, bestie · page: bk clone(none) — xoxo, that’s the whole footer. 💖