mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

change name of buprepo

Browse source 
Instead of remote=, use buprepo=

Anyone already using bup will need to re-run git annex initremote.
This commit is contained in:
Joey Hess 2011-04-09 12:41:17 -04:00
parent 141e55ff11
commit c739c7d787
3 changed files with 35 additions and 29 deletions
Download patch file Download diff file Expand all files Collapse all files

6
doc/special_remotes/bup.mdwn
View file

@ -21,10 +21,10 @@ These parameters can be passed to `git annex initremote` to configure bup:
keys can be given access to a remote by rerunning initremote with
the new key id.
* `remote` - Required. This is passed to `bup` as the `--remote`
* `buprepo` - Required. This is passed to `bup` as the `--remote`
to use to store data. To create the repository,`bup init` will be run.
Example: "remote=example.com:/big/mybup" or "remote=/big/mybup"
(To use the default `~/.bup` repository on the local host, specify "remote=")
Example: "buprepo=example.com:/big/mybup" or "buprepo=/big/mybup"
(To use the default `~/.bup` repository on the local host, specify "buprepo=")
Options to pass to `bup split` when sending content to bup can also
be specified, by using `git config annex.bup-split-options`. This

4
doc/walkthrough/using_bup.mdwn
View file

@ -8,10 +8,10 @@ Here's how to create a bup remote, and describe it.
[[!template id=note text="""
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".
"buprepo=/big/mybup".
"""]]
# git annex initremote mybup type=bup encryption=none remote=example.com:/big/mybup
# git annex initremote mybup type=bup encryption=none buprepo=example.com:/big/mybup
initremote bup (bup init)
Initialized empty Git repository in /big/mybup/
ok