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

response

Browse source
This commit is contained in:
Joey Hess 2017-02-14 14:21:58 -04:00
parent de19340d7f
commit 3aecb1d059
No known key found for this signature in database
GPG key ID: C910D9222512E3C7
1 changed files with 21 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

21
doc/git-annex-enableremote/comment_2_43876327581d6bcfb69c318c02d6389a._comment Normal file
View file

@ -0,0 +1,21 @@
[[!comment format=mdwn
username="joey"
subject="""comment 2"""
date="2017-02-14T18:16:52Z"
content="""
@Sundar, good question.
`git annex enableremote` will always refuse to enable the remote if there's
a missing parameter, and prompt for the parameter. Finding the right value
is up to you. Most of the time, no additional parameters are needed, or
the parameters are fairly self-explanatory, eg login passwords for remote
services.
The difficulty with directory special remotes is that my /foo may not be
the same as your /foo, so it can't reuse the directory= that was provided
to initremote, and it's up to you to enter the right directory path.
I think this needs to come down to documentation in the repository. The
description of the remote (set by `git annex describe`
is a reasonable place to put that, unless you have somewhere better.
"""]]