/usr/share/doc/bup/bup-join.html is in bup-doc 0.29-3.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta http-equiv="Content-Style-Type" content="text/css" />
<meta name="generator" content="pandoc" />
<meta name="author" content="Avery Pennarun apenwarr@gmail.com" />
<meta name="date" content="2017-04-01" />
<title>bup-join(1) Bup debian/0.29-3</title>
<style type="text/css">code{white-space: pre;}</style>
</head>
<body>
<div id="header">
<h1 class="title">bup-join(1) Bup debian/0.29-3</h1>
<h2 class="author">Avery Pennarun <a href="mailto:apenwarr@gmail.com">apenwarr@gmail.com</a></h2>
<h3 class="date">2017-04-01</h3>
</div>
<h1 id="name">NAME</h1>
<p>bup-join - concatenate files from a bup repository</p>
<h1 id="synopsis">SYNOPSIS</h1>
<p>bup join [-r <em>host</em>:<em>path</em>] [refs or hashes...]</p>
<h1 id="description">DESCRIPTION</h1>
<p><code>bup join</code> is roughly the opposite operation to <code>bup-split</code>(1). You can use it to retrieve the contents of a file from a local or remote bup repository.</p>
<p>The supplied list of refs or hashes can be in any format accepted by <code>git</code>(1), including branch names, commit ids, tree ids, or blob ids.</p>
<p>If no refs or hashes are given on the command line, <code>bup join</code> reads them from stdin instead.</p>
<h1 id="options">OPTIONS</h1>
<dl>
<dt>-r, --remote=<em>host</em>:<em>path</em></dt>
<dd>Retrieves objects from the given remote repository instead of the local one. <em>path</em> may be blank, in which case the default remote repository is used. The connection to the remote server is made with SSH. If you'd like to specify which port, user or private key to use for the SSH connection, we recommend you use the <code>~/.ssh/config</code> file. Even though the data source is remote, a local bup repository is still required.
</dd>
</dl>
<h1 id="examples">EXAMPLES</h1>
<pre><code># split and then rejoin a file using its tree id
TREE=$(tar -cvf - /etc | bup split -t)
bup join $TREE | tar -tf -
# make two backups, then get the second-most-recent.
# mybackup~1 is git(1) notation for the second most
# recent commit on the branch named mybackup.
tar -cvf - /etc | bup split -n mybackup
tar -cvf - /etc | bup split -n mybackup
bup join mybackup~1 | tar -tf -</code></pre>
<h1 id="see-also">SEE ALSO</h1>
<p><code>bup-split</code>(1), <code>bup-save</code>(1), <code>bup-cat-file</code>, <code>ssh_config</code>(5)</p>
<h1 id="bup">BUP</h1>
<p>Part of the <code>bup</code>(1) suite.</p>
</body>
</html>
|