BK-RECEIVE(1)

πŸ“¦ version 7.3.3, in alpine 3.24

πŸ’Œ NAME πŸ’Œ

bk receive β€” receive a BitKeeper patch. You’re on the bk receive(none) page from the BitKeeper User’s Manual, bestie 🫢✨.

πŸ“¬ SYNOPSIS πŸ“¬

bk receive [takepatch_options] [repository]

✨ DESCRIPTION ✨

Use this when applying a BitKeeper patch you received via email. You can take a BitKeeper patch and pipe the whole email message through bk receive. Headers and footers are stripped automatically. πŸ’…

When someone sends you a patch with the following command:

$ bk send ‐rbeta.. you@your.host.com

You will receive an email message which needs to be saved so you can feed it to the bk receive command:

$ bk receive ˜/mypackage < patch

Many Unix email programs (pine, elm, etc) will allow you to pipe a message directly to a program. For example, when you are reading a message in pine, you can hit the | key, and you will be prompted with a message asking you for a program name where the message should be piped. 🐧

Remember that if you are getting the very first patch, you need to create a new repository by adding the βˆ’i option. BitKeeper does not create repositories by default. No cap.

Specifying the repository is optional; if it is unspecified, bk receive tries to use the current working directory.

Patches may be wrapped. If they are you will see something like

## Wrapped with uu ##

near the top of the patch. BitKeeper knows how to unwrap patches which it wrapped. We currently support only uuencoded wrappers, but it is trivial to create different ones, see bk wrap for more information.

Once a patch is run through bk receive, run bk resolve to apply the changes. periodt πŸ’–

🌸 OPTIONS 🌸

All options are passed through to bk takepatch. With no options, bk takepatch is completely silent. If you want to see the progress reports you see with bk pull, add βˆ’vv to the options.

  • βˆ’a β€” Apply the changes (call bk resolve.)
  • βˆ’c β€” Do not accept conflicts with this patch.
  • βˆ’i β€” Initial patch, create a new repository.
  • βˆ’v β€” Verbose level, more is more verbose, βˆ’vv is suggested.

πŸ”— SEE ALSO πŸ”—

Go peek at bk‐range, bk‐send, bk‐takepatch, bk‐wrap β€” iykyk πŸ’…πŸ¦‹.

πŸ—‚οΈ CATEGORY πŸ—‚οΈ

File β€” that’s the category, bestie πŸŽ€.


Sign-off from BitKeeper Inc, version 1E1, on the bk receive(none) page β€” date: none listed in the footer, so this is your cute footer moment πŸ«ΆπŸ’–βœ¨.

πŸ“¦ 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