bup-get(1) | bup-get(1) |
bup-get - copy repository items (CAUTION: EXPERIMENTAL)
bup get [-s source-path] [-r host:path] OPTIONS <(METHOD ref [dest])>...
bup get copies the indicated refs from the source repository to the destination repository (respecting --bup-dir and BUP_DIR), according to the specified METHOD, which may be one of --ff, --ff:, --append, --append:, --pick, --pick:, --force-pick, --force-pick:, --new-tag, --new-tag:, --replace, --replace:, or --unnamed. See the EXAMPLES below for a quick introduction.
The ref is the source repository reference of the object to be fetched, and the dest is the optional destination reference. A dest may only be specified for a METHOD whose name ends in a colon. For example:
bup get -s /source/repo --ff foo bup get -s /source/repo --ff: foo/latest bar bup get -s /source/repo --pick: foo/2010-10-10-101010 .tag/bar
As a special case, if ref names the “latest” save symlink, then bup will act exactly as if the save that “latest” points to had been specified, rather than the “latest” symlink itself, so bup get foo/latest will actually be interpreted as something like bup get foo/2013-01-01-030405.
In some situations bup get will evaluate a branch operation according to whether or not it will be a “fast-forward” (which requires that any existing destination branch be an ancestor of the source).
An existing destination tag can only be overwritten by a --replace or --force-pick.
When a new commit is created (i.e. via --append, --pick, etc.), it will have the same author, author date, and message as the original, but a committer and committer date corresponding to the current user and time.
If requested by the appropriate options, bup will print the commit, tree, or tag hash for each destination reference updated. When relevant, the tree hash will be printed before the commit hash.
Local refs can be pushed to a remote repository with the --remote option, and remote refs can be pulled into a local repository via “bup on HOST get ...”. See bup-on(1) and the EXAMPLES below for further information.
WARNING: This is one of the few bup commands that can modify your archives in intentionally destructive ways. Though if an attempt to join or restore the data you still care about succeeds after you’ve run this command, then that’s a fairly encouraging sign that it worked correctly. (The dev/compare-trees command in the source tree can be used to help test before/after results.)
# Update or copy the archives branch in src-repo to the local repository. $ bup get -s src-repo --ff archives # Append a particular archives save to the pruned-archives branch. $ bup get -s src-repo --pick: archives/2013-01-01-030405 pruned-archives # Update or copy the archives branch on remotehost to the local # repository. $ bup on remotehost get --ff archives # Update or copy the local branch archives to remotehost. $ bup get -r remotehost: --ff archives # Update or copy the archives branch in src-repo to remotehost. $ bup get -s src-repo -r remotehost: --ff archives # Update the archives-2 branch on remotehost to match archives. # If archives-2 exists and is not an ancestor of archives, bup # will refuse. $ bup get -r remotehost: --ff: archives archives-2 # Replace the contents of branch y with those of x. $ bup get --replace: x y # Copy the latest local save from the archives branch to the # remote tag foo. $ bup get -r remotehost: --pick: archives/latest .tag/foo # Or if foo already exists: $ bup get -r remotehost: --force-pick: archives/latest .tag/foo # Append foo (from above) to the local other-archives branch. $ bup on remotehost get --append: .tag/foo other-archives # Append only the /home directory from archives/latest to only-home. $ bup get -s "$BUP_DIR" --append: archives/latest/home only-home
Part of the bup(1) suite.
Rob Browning <rlb@defaultvalue.org>.
0.33.2 | Bup 0.33.2 |