mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Added a comment

Browse source
This commit is contained in:
https://www.google.com/accounts/o8/id?id=AItOawln3ckqKx0x_xDZMYwa9Q1bn4I06oWjkog 2013-07-25 19:16:20 +00:00 • committed by admin
parent a9b9cdef91
commit 8d2a8c7365
1 changed files with 14 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
doc/forum/archival_and_multiple_users/comment_3_bd44634b04732ffb91154c61ef9cf828._comment Normal file
View file

@ -0,0 +1,14 @@
[[!comment format=mdwn
username="https://www.google.com/accounts/o8/id?id=AItOawln3ckqKx0x_xDZMYwa9Q1bn4I06oWjkog"
nickname="Michael"
subject="comment 3"
date="2013-07-25T19:16:20Z"
content="""
> The way to handle this situation is to copy or move the files you want out of the archive directory, and back to the parent directory. This move of the file will be synced from your repository to all the other repositories. When the repository that does have access to the archive notices this, it will get the files that have been moved out of the archive. Normal assistant syncing will then arrange to get them transferred back to the repository of the user who had wanted them.
But won't it also transfer the same files into repos of all other users (who didn't want the files)?
On a related note, allowing moving files for everyone could jeopardise integrity of the master archive. Is there a way to limit what kind of ops the users can do (e.g. copy but not move)?
Re offline drives, the case I was thinking of is actually where each user has access to e.g. special remotes directly. So a manual get/put would solve the problem at hand.
"""]]