diff options
author | divB <divB@web> | 2014-07-17 04:58:21 +0000 |
---|---|---|
committer | admin <admin@branchable.com> | 2014-07-17 04:58:21 +0000 |
commit | 7a5db71abd3089bffeccbbeb910179a77af1afdd (patch) | |
tree | 0f000b1710c917c08e838122ff558d050e4976c4 | |
parent | c8295b7d487307a4873d77132a5abf45740f53c4 (diff) |
-rw-r--r-- | doc/forum/comprehension_question:_repository_vs._working_copy_in_direct_mode.mdwn | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/forum/comprehension_question:_repository_vs._working_copy_in_direct_mode.mdwn b/doc/forum/comprehension_question:_repository_vs._working_copy_in_direct_mode.mdwn new file mode 100644 index 000000000..350bcd7bd --- /dev/null +++ b/doc/forum/comprehension_question:_repository_vs._working_copy_in_direct_mode.mdwn @@ -0,0 +1,10 @@ +(I put this in a separate topic because it is a different question) + +I still do not fully understand when (in direct mode!) a file is in the work copy and when in the repository. +Because what git-annex always refers to a "repository" is actually a repository (i.e., the server part for subversion) *and* a work copy (the client part in subversion), right? (except for bare repositories which have only the former) + +When I change a file in the work copy, I still need to "git annex sync", right? But do I also need to "git annex sync --content" to move the changes from the work copy to the repository? + +Because I have a headless server where the annex should also be accessed via samba. When files are added/changed, the annex clients do not see the changes until I manually do a couple of "git annex sync" and "git annex sync --content" (it's not deterministic yet for me how often). + +Is this the intended behavior? If yes, is there a better way to automatically sync the changes on the headless server other than a cron job? |