BK-MV(1)

💅 NAME 💅

bk mv − rename file[s] ✨

okay bestie, this is the bk mv page from the BitKeeper User’s Manual — yes, the one that renames files. No cap. 🫶

✨ SYNOPSIS ✨

bk mv [−f] source‐file‐or‐dir [file ...]  dest‐file‐or‐dir

🦋 DESCRIPTION 🦋

To rename a file/directory from A to B do this:

$ bk mv A B

The bk mv command will rename the checked out file (if any) as well as the revision control file. Edited files are also renamed and then re-edited, preserving any changes made but not yet checked in. The rename will appear as an additional change to the file when you commit the next changeset. 🎀

Renames propagate just like content changes, i.e., they happen automatically when you pull changes into your repository from another repository unless you have also renamed the file. In that case, the resolver will prompt you to choose a name. 🦋

If the last argument is an existing directory, bk mv moves all listed files into that directory. Otherwise, if only two files are given, it renames the first as the second. It is an error if more than two files are listed and the last argument is not a directory. The intent is that bk mv behaves like the traditional UNIX mv command, except that it knows about the additional BitKeeper files and records the rename event. 👑

🎀 NOTES 🎀

• metafile refusal: bk mv will refuse to move BitKeeper metafiles without the −f option (use of which is not recommended). 🙈
• directory check: if both the A and B arguments are directories, bk mv will check the repository consistency. If this check fails the move operation will not continue. 💀

🔥 SEE ALSO 🔥

bk‐commit, bk‐names, bk‐pull, bk‐push, bk‐rm, bk‐rmdir

👑 CATEGORY 👑

• Common
• File

---

💖 that’s the whole page! footer vibes: BitKeeper Inc, version 1E1, and bk mv(none) — with the date slot giving none. mwah, bye bestie! 💅