export --fast sets up but does not populate export
sync --content finishes
This commit is contained in:
parent
2e69efea8d
commit
a6c0ed6698
2 changed files with 8 additions and 1 deletions
|
@ -82,7 +82,8 @@ seek o = do
|
||||||
db <- openDb (uuid r)
|
db <- openDb (uuid r)
|
||||||
ea <- exportActions r
|
ea <- exportActions r
|
||||||
changeExport r ea db new
|
changeExport r ea db new
|
||||||
void $ fillExport r ea db new
|
unlessM (Annex.getState Annex.fast) $
|
||||||
|
void $ fillExport r ea db new
|
||||||
closeDb db
|
closeDb db
|
||||||
|
|
||||||
-- | Changes what's exported to the remote. Does not upload any new
|
-- | Changes what's exported to the remote. Does not upload any new
|
||||||
|
|
|
@ -50,6 +50,12 @@ And, git-annex will never trust an export to retain the content of a key.
|
||||||
the branch. `git annex sync --content` and the git-annex assistant
|
the branch. `git annex sync --content` and the git-annex assistant
|
||||||
will update exports when it commits to the branch they are tracking.
|
will update exports when it commits to the branch they are tracking.
|
||||||
|
|
||||||
|
* `--fast`
|
||||||
|
|
||||||
|
This sets up an export of a tree, but avoids any expensive file uploads to
|
||||||
|
the remote. You can later run `git annex sync --content` to upload
|
||||||
|
the files to the export.
|
||||||
|
|
||||||
# EXAMPLE
|
# EXAMPLE
|
||||||
|
|
||||||
git annex initremote myexport type=directory directory=/mnt/myexport \
|
git annex initremote myexport type=directory directory=/mnt/myexport \
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue