summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar https://www.google.com/accounts/o8/id?id=AItOawln3ckqKx0x_xDZMYwa9Q1bn4I06oWjkog <Michael@web>2013-07-24 14:59:25 +0000
committerGravatar admin <admin@branchable.com>2013-07-24 14:59:25 +0000
commit53850bc2a38a943ddbf11e4a2e4033c4d75446c7 (patch)
tree5a9bf2c0ca743501ce4dcf99eb9a72a210ce91fd /doc
parentd4ee455b47393f7eb1c6b4bfd3267aacba20f81c (diff)
Diffstat (limited to 'doc')
-rw-r--r--doc/forum/archival_and_multiple_users.mdwn8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/forum/archival_and_multiple_users.mdwn b/doc/forum/archival_and_multiple_users.mdwn
new file mode 100644
index 000000000..da451d9fb
--- /dev/null
+++ b/doc/forum/archival_and_multiple_users.mdwn
@@ -0,0 +1,8 @@
+The assistant archival walk-through describes how files get removed from local repo if moved into archive repos.
+What if the files in question aren't needed immediately (and can be archived) for one user of a shared repo, but needed by someone else on their own machine?
+git-annex directory arrangement propagation wouldn't work for this case, it seems. Could assistant handle this case?
+
+It looks like having a browser of the directory tree in git-annex assistant webpage with say right-click menu with "get" and "drop" would be the most flexible.
+
+Or maybe it could be more about integration with Linux etc file browsers (but then it's system specific, unlike with webapp).
+