From a6de9a616ec14e333af16a13eb34245e84811559 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawln3ckqKx0x_xDZMYwa9Q1bn4I06oWjkog" Date: Wed, 24 Jul 2013 14:59:25 +0000 Subject: [PATCH] --- doc/forum/archival_and_multiple_users.mdwn | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/archival_and_multiple_users.mdwn diff --git a/doc/forum/archival_and_multiple_users.mdwn b/doc/forum/archival_and_multiple_users.mdwn new file mode 100644 index 0000000000..da451d9fb9 --- /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). +