diff options
| author |  https://www.google.com/accounts/o8/id?id=AItOawnh6wz0pMA3NLPFg2j_I3S5JeinaOVqnng <Felix@web> | 2013-09-11 20:01:06 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2013-09-11 20:01:06 +0000 |
| commit | 7c8d2207fcc4f849d7e0abe3bf5303e1d1b425b4 (patch) | |
| tree | ddb2a9a4149508744f3de221da334914a10d0140 | |
| parent | 9ac8980b4bb654843216233d7a2ad3d8c2ea9b5e (diff) | |
| -rw-r--r-- | doc/forum/Use_case_with_syncing_only_a_subset_possible__63__.mdwn | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/forum/Use_case_with_syncing_only_a_subset_possible__63__.mdwn b/doc/forum/Use_case_with_syncing_only_a_subset_possible__63__.mdwn new file mode 100644 index 000000000..0d102b0d4 --- /dev/null +++ b/doc/forum/Use_case_with_syncing_only_a_subset_possible__63__.mdwn @@ -0,0 +1,13 @@ +I'm trying to figure out if git-annex can be used for the following use case: + +- 2 repos in direct mode A and B +- A is on a local filesystem, B could be a NFS mountpoint or ssh +- B contains a number of toplevel directories, A contains a subset of those +- For the subset in A all changes in those directories that happen on A or B should be synced automatically between both repos, including file removals. +- A can decide to not carry a toplevel dir any more, but it must still exist in B. +- A can copy new toplevel dirs from B and those should be synced from then on. + +I've been looking at the docs and played with two test repos, but I cannot seem to make the above work. To me it looks like I would need a possibility include/exclude paths from syncing via a regex. + +Thanks, +Felix |