diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2017-02-07 15:10:41 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2017-02-07 15:10:41 -0400 |
| commit | c8d5b2067037ecb56c06cd1cc32f248c463ed228 (patch) | |
| tree | 970d8d0a20d6670e8818ea6b733d96065c92ef95 /doc/git-annex-initremote.mdwn | |
| parent | dc0f824c1bc4c9aac1045894983a434eb26196ab (diff) | |
initremote: When a uuid= parameter is passed, use the specified UUID for the new special remote, instead of generating a UUID.
This can be useful in some situations, eg when the same data can be
accessed via two different special remote backends.
Diffstat (limited to 'doc/git-annex-initremote.mdwn')
| -rw-r--r-- | doc/git-annex-initremote.mdwn | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/git-annex-initremote.mdwn b/doc/git-annex-initremote.mdwn index 1b46ff536..d47c66506 100644 --- a/doc/git-annex-initremote.mdwn +++ b/doc/git-annex-initremote.mdwn @@ -33,6 +33,12 @@ is run in a new clone, it will attempt to enable the special remote. Of course, this works best when the special remote does not need anything special to be done to get it enabled. +Normally, git-annex generates a new UUID for the new special remote. +If you want to, you can specify a UUID for it to use, by passing a +uuid=whatever parameter. This can be useful in some situations, eg when the +same data can be accessed via two different special remote backends. +But if in doubt, don't do this. + # OPTIONS * `--fast` |