BK-EXPORT(1)

💅 BK-EXPORT(1) 💅

okay so welcome to the BitKeeper User’s Manual, bestie — this is the page for bk export(none), and it’s literally about exporting a patch or a version of a BitKeeper repository. ✨

🌸 NAME 🌸

bk export − export a patch or version of a BitKeeper repository. 🫶

✨ SYNOPSIS ✨

Two moods, bestie:

bk export −tpatch [−ahpST] [−salias] [−ipat] [−xpat] −rr1,r2
bk export −tplain [−akSTvw] [−salias] [−ipat] [−xpat] −rrev to

tiny heads-up: −salias shows up in the synopsis, but the original OPTIONS list doesn’t give it a separate description. No invented lore here. 🙈

🦋 DESCRIPTION 🦋

bk export generates a directory tree alongside the BitKeeper repository, and that tree contains checked-out copies of all the files under BitKeeper control. 💖 It can also generate traditional (diff −Nur) patches between any two revisions of the source tree. 🔥

By default, bk export only exports user files. Files under the BitKeeper directory are not exported. This behavior can be changed with the −i and −x options. 👑

🎀 OPTIONS 🎀

• −a — include system files from BitKeeper/ subdirectory in exports. 📁
• −h — disable patch header. 🙅‍♀️
• −ipat — export only pathnames matching pat pattern (see below). 🎯
• −k — do not expand keywords (default is to expand keywords). 🔑
• −p — do procedural diffs when exporting a patch (see diff(1)). 🧵
• −rrev — export the tree as of revision rev. 🌳
• −T — set gfile modification time to check-in time. ⏰
• −ttype — select export format via type:
  • plain — export file in plain text to a directory tree. 📄
  • patch — export file in gnu patch format. 🩹
• −v — be verbose. 🗣️
• −w — make files writable (default is read-only). ✍️
• −xpat — export all pathnames not matching pat pattern (see below). 🚫
• −salias — appears in the synopsis; no separate description in the original OPTIONS list. 🫡

🌈 INCLUDE/EXCLUDE PROCESSING 🌈

Include and/or exclude patterns may be used to control which files are exported. There may be multiple include and/or exclude patterns. 🧚 The patterns are a file glob the same as used by bk glob. Patterns are matched against the partial pathname from the root of the repository. If the partial pathname matches any of the exclude patterns then the file is skipped. If there are one or more include patterns but the partial pathname does not match any of the include patterns then the file is skipped. Exclude processing takes precedence over include processing. 👑

When exporting patches there can be ambiguity as to which name is used for include/exclude processing because some files may have been moved in the changes implied by the exported patch. The include/exclude processing always applies to any of file names contained in the changes implied by the patch. 🌀

For example, suppose you have a file that is currently deleted but at the time of the patch was in src/foo.c. If you told the system to export src/* then the file will be in the set. 💅

🔗 SEE ALSO 🔗

diff(1), patch(1), bk‐glob, bk‐rset — go read those too, bestie. 🫶

🏷️ CATEGORY 🏷️

Compat — yes, that’s the category. 👑

---

okay that’s the whole page, bestie. Footer shoutout: BitKeeper Inc · version 1E1 · bk export(none). The original footer doesn’t print a separate date, so no fake date energy here. 💖