BK-FAST-EXPORT(1)

💖 NAME 💖

This is BK-FAST-EXPORT(1) — the BitKeeper User’s Manual page for bk fast‐export(none), aka bk fast‐export — and bestie, it literally exports the whole repository in a format compatible with git. 💅✨

---

✨ SYNOPSIS ✨

bk fast‐export options

---

🦋 DESCRIPTION 🦋

bk fast‐export exports the entire repository in a format suitable for input to git’s fast-import command. The output is sent to standard output. No cap.

By default, the BitKeeper MD5KEY of the equivalent changeset will be added to every commit in git. 💖

---

🎀 OPTIONS 🎀

• −Afilename, −−authors=filename — use the given file as a map for authors. The syntax is compatible with git cvsimport:

    USER = Name <email@domain.com>

With one user per line. 🫶

• −−branch=branch — by default the export will be done for the "master" git branch. This option lets you do the export for a different branch. This is useful for exporting two different BitKeeper branches (e.g. "dev" and "stable") into the same git repository. See SUGGESTED USE below. 👑
• −−incremental=<repo> — do an incremental export starting from the last exported cset found in the Git repository repo. This will not work if the previous export used −−no−bk−keys. 💀
• −−no−bk−keys — don’t add the "bk: <mk5key>" line at the end of the comments (incompatible with −−incremental). 🙈
• −q, −−quiet — don’t print warnings or other information. 🤫
• −S, −−standalone — when used in a nested collection, export only the product or the component implied by the current working directory. 🧚

---

🌈 EXAMPLES 🌈

The commands to export a BitKeeper repository named "bk‐repo" to a git repository named "git‐repo" would be:

$ git init git‐repo
$ (cd bk‐repo; bk fast‐export) | (cd git‐repo ; git fast‐import)

And to do an incremental export later:

$ (cd bk‐repo; bk fast‐export ‐‐incremental=../git‐repo) | \
  (cd git‐repo ; git fast‐import)

---

🌸 SUGGESTED USE 🌸

It is suggested that you create a pristine import branch where no git commits are created. By default, fast‐export warns if the latest commit in the import branch is not marked with a BitKeper key (this can be disabled with the −−quiet option). 👀

For example, if you have two separate BitKeeper branches: ’dev’, and ’stable’, you can import each of them into corresponding git branches and pass the appropriate −−branch option to fast‐export each time. If the git repository is also being developed, this can be done in a separate git branch (e.g. ’master’). 💖

---

⭐ EXIT STATUS ⭐

bk fast‐export returns exit status 0 if the export completed successfully. Non-zero if there was an error. Periodt. 💅

---

🦋 SEE ALSO 🦋

bk‐fast‐import

---

👑 CATEGORY 👑

Utility

---

Cute sign-off: source/version BitKeeper Inc + 1E1 for bk fast‐export(none) — and no separate date is printed in this footer. That’s the page, bestie. 💖🫶