bk(none)

πŸ“¦ version 7.3.3, in alpine 3.24

πŸ’– NAME πŸ’–

okay so this is the bk(none) page from the BitKeeper User’s Manual, and bk is the BitKeeper configuration management system front end. periodt. 🫢

✨ SYNOPSIS ✨

bk [βˆ’A|U|e|r] [βˆ’salias] [options] command [options]

πŸ¦‹ DESCRIPTION πŸ¦‹

bk is the front end to all BitKeeper commands, bestie. ✨

If you’re looking for instructions on how to get started, try running the test drive at http://www.bitkeeper.com/Test.html πŸ˜­πŸ’–.

πŸ‘‘ OPTIONS πŸ‘‘

Only the global options are documented here. To see command specific options consult the documentation for the command in question (bk help command). iykyk πŸ’…
  • βˆ’@[url] β€” run the command in the specified repository rather than locally. If url is not specified, then use the parent[s] of the current repository. If there are multiple parents, incoming and/or outgoing, use all of those parents. You can use the construct βˆ’@@file to specify a file containing a list of repository URLs, one per line; the command is run in each of the remote repositories. πŸ¦‹
    • The βˆ’r[dir] option works as expected, running the command recursively over all of the implied files. If specified, dir must be relative to the root of the remote repository.
    • If - is the last argument, then the standard input is read and buffered. Each remote command receives the same input.
  • βˆ’A, βˆ’βˆ’all‐files β€” starting at the current working directory, run command on all files in the entire repository or nested collection. In a standalone repository this option is lowkey similar to βˆ’r. For example, to search all files in a nested collection:
$ bk ‐A grep ’the string I want to find’

See βˆ’s below for ways to limit the set of files processed in a nested collection. 🌸

  • ‐‐config=key:val β€” override one value in the configuration for this command only.
  • ‐‐cd=dir β€” change to dir before running the command.
  • βˆ’β€headers β€” for remote commands (βˆ’@) this option causes the output from running the command in each repository to prefixed with a header:
#### repo‐url or location ####
  • βˆ’R β€” change directories to the root of the repository before running command.
  • βˆ’r[dir] β€” starting at dir, or the repository root if dir was not specified, apply command recursively to dir and all subdirectories. This works by generating a list of files and passing them to command on the standard input. This option differs from βˆ’A in that it is limited to the current repository only, so if you are in a component it will list only files belonging to that component. the way that's so specific πŸ’…
  • βˆ’1acGpx βˆ’Λ†G β€” one or more of these options may be used in combination with βˆ’A, βˆ’r, or βˆ’U to limit the set of files passed to command. πŸ‘‘
    • βˆ’1 β€” only examine the current (or named) directory. Do not go into subdirectories.
    • βˆ’G β€” list files only if they are checked out ("gotten").
    • βˆ’Λ†G β€” list files only if they are not checked out ("not gotten").
    • βˆ’a β€” examine all files, even if listed in BitKeeper/etc/ignore.
    • βˆ’c β€” list changed files (locked and modified). See EXAMPLES below for a typical usage.
    • βˆ’p β€” list files with pending deltas.
    • βˆ’x β€” list files which have no revision control files. See EXAMPLES below for a typical usage.
    • βˆ’βˆ’gfiles‐opts=opts β€” this long option may be used to pass any valid option to sfiles. The format must include the leading βˆ’ or βˆ’βˆ’ for each option and each option must be separated by a space like so:
βˆ’βˆ’gfiles‐opts=’‐c ‐‐cold’

πŸ’€ EXIT STATUS πŸ’€

Unless otherwise documented, all BitKeeper commands return exit status 0 on success and greater than 0 on failure. fr fr, zero is the slay outcome and greater-than-zero is the vibe check fail. 😭

🌈 EXAMPLES 🌈

The following commands are equivalent:

bk ‐A get
bk ‐R gfiles | bk ‐R get ‐
cd `bk root`; bk gfiles | bk get ‐

An example usage for generating a patch of all new and/or changed files:

$ bk ‐cxU diff ‐Nu

πŸ“ SEE ALSO πŸ“

bk‐gfiles β€” go say hi, bestie πŸ¦‹

πŸŽ€ CATEGORY πŸŽ€

Repository β€” that’s the category, main character energy only. πŸ‘‘


sign-off slay: this footer is brought to you by BitKeeper Inc, version 1E1, manual name bk(none) β€” no separate date shown in this footer, bestie, just source/version vibes and a whole lot of πŸ’–βœ¨.

πŸ“¦ where this page comes from
  • alpine 3.24: bitkeeper-doc 7.3.3-r1 Β· Apache-2.0
  • πŸ’– girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms