summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2011-04-08 20:44:52 -0400
committerGravatar Joey Hess <joey@kitenet.net>2011-04-08 20:44:52 -0400
commit5d7ef05d95dc2a8e926a87cf552b119457231db0 (patch)
treeb79b16b641ac5b2a868a577c25ab70580cf8cd92
parent939c88787ad785a9d00e376b8417ab6a5c40b339 (diff)
local bup remotes
-rw-r--r--doc/special_remotes/bup.mdwn4
-rw-r--r--doc/walkthrough/using_bup.mdwn6
2 files changed, 8 insertions, 2 deletions
diff --git a/doc/special_remotes/bup.mdwn b/doc/special_remotes/bup.mdwn
index 950b64e9c..4872072a0 100644
--- a/doc/special_remotes/bup.mdwn
+++ b/doc/special_remotes/bup.mdwn
@@ -22,8 +22,8 @@ These parameters can be passed to `git annex initremote` to configure bup:
the new key id.
* `remote` - Required. This is passed to `bup` as the `--remote`
- to use to store data. `bup init` will be run to create the
- repository. Example: "remote=example.com:/big/mybup"
+ to use to store data. To create the repository,`bup init` will be run.
+ Example: "remote=example.com:/big/mybup" or "remote=/big/mybup"
Options to pass to `bup split` when sending content to bup can also
be specified, by using `git config annex.bup-split-options`. This
diff --git a/doc/walkthrough/using_bup.mdwn b/doc/walkthrough/using_bup.mdwn
index 7ba9d1fce..4ce189480 100644
--- a/doc/walkthrough/using_bup.mdwn
+++ b/doc/walkthrough/using_bup.mdwn
@@ -5,6 +5,12 @@ git-annex, you can have git on both the frontend and the backend.
Here's how to create a bup remote, and describe it.
+[[!template id=note test="""
+Instead of specifying a remote system, you could choose to make a bup
+remote that is only accessible on the current system, by passing
+"remote=/big/mybup".
+"""]
+
# git annex initremote mybup type=bup encryption=none remote=example.com:/big/mybup
initremote bup (bup init)
Initialized empty Git repository in /big/mybup/