p2p: --link no longer takes a remote name, instead the --name option can be used.
This commit is contained in:
parent
76d525c4d5
commit
e67a310da1
4 changed files with 39 additions and 13 deletions
|
@ -22,14 +22,20 @@ services.
|
|||
over the available P2P networks. The address or addresses is output to
|
||||
stdout.
|
||||
|
||||
* `--link remotename`
|
||||
* `--link`
|
||||
|
||||
Sets up a git remote with the specified remotename that is accessed over
|
||||
a P2P network.
|
||||
Sets up a git remote that is accessed over a P2P network.
|
||||
|
||||
This will prompt for an address to be entered; you should paste in the
|
||||
address that was generated by --gen-address in the remote repository.
|
||||
|
||||
Defaults to making the git remote be named "peer1", "peer2",
|
||||
etc. This can be overridden with the `--name` option.
|
||||
|
||||
* `--name`
|
||||
|
||||
Specify a name to use when setting up a git remote.
|
||||
|
||||
# SEE ALSO
|
||||
|
||||
[[git-annex]](1)
|
||||
|
|
|
@ -46,7 +46,7 @@ Now, tell the new peer about the address of the first peer.
|
|||
This will make a git remote named "peer1", which connects,
|
||||
through Tor, to the repository on the other peer.
|
||||
|
||||
git annex p2p --link peer1
|
||||
git annex p2p --link --name peer1
|
||||
|
||||
That command will prompt for an address; paste in the address that was
|
||||
generated on the first peer, and then press Enter.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue