update docs to account for exporttree
This commit is contained in:
parent
722bb79dbf
commit
00b29d17ad
2 changed files with 14 additions and 5 deletions
|
@ -5,11 +5,13 @@ you want to use to sneakernet files between systems (possibly with
|
||||||
[[encrypted|encryption]] contents). Just set up both systems to use
|
[[encrypted|encryption]] contents). Just set up both systems to use
|
||||||
the drive's mountpoint as a directory remote.
|
the drive's mountpoint as a directory remote.
|
||||||
|
|
||||||
Note that directory remotes have a special directory structure
|
With the exporttree=yes parameter, the directory contains a tree of files
|
||||||
(by design, the same as the [[rsync|rsync]] remote).
|
with the same filenames used in a branch of your repository. Without that
|
||||||
If you just want two copies of your repository with the files "visible"
|
parameter, the directory contains a directory structure similar to
|
||||||
in the tree in both, the directory special remote is not what you want.
|
`.git/annex/objects` or other special remotes like [[rsync]].
|
||||||
Instead, you should use a regular `git clone` of your git-annex repository.
|
|
||||||
|
Bear in mind that you can also use a regular `git clone` of your git-annex
|
||||||
|
repository, rather than a directory remote.
|
||||||
|
|
||||||
## configuration
|
## configuration
|
||||||
|
|
||||||
|
|
|
@ -0,0 +1,7 @@
|
||||||
|
[[!comment format=mdwn
|
||||||
|
username="joey"
|
||||||
|
subject="""Re: File visibility"""
|
||||||
|
date="2023-04-25T16:14:50Z"
|
||||||
|
content="""
|
||||||
|
Yes, that warning predated the exporttree feature. I've updated the docs.
|
||||||
|
"""]]
|
Loading…
Reference in a new issue