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

Merge branch 'master' of ssh://git-annex.branchable.com

Browse source
This commit is contained in:
Joey Hess 2013-07-25 15:45:39 -04:00
commit 2f15c192dd
4 changed files with 47 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
doc/design/assistant/comment_20_099da245e3276fa84f5e14312d186621._comment Normal file
View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="http://joeyh.name/"
ip="2001:4978:f:21a::2"
subject="comment 20"
date="2013-07-25T18:22:51Z"
content="""
@Georg, DMG have been built for OSX for a long time. See [[install/OSX]]
"""]]

12
doc/forum/archival_and_multiple_users/comment_2_a96d57d4bb567ac9b0b9167d5b1be011._comment Normal file
View file

@ -0,0 +1,12 @@
[[!comment format=mdwn
username="http://joeyh.name/"
ip="2001:4978:f:21a::2"
subject="comment 2"
date="2013-07-25T18:42:59Z"
content="""
I believe that the world has enough (or too many) file managers, and do not want to build another one just for git-annex. In any case \"git annex get\" or any GUI wrapping around it is not going to help with the described use case, because the problem is that the files are archived away in my offline drive, while you want to access them in your repository, which does not have access to that drive.
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.
Of course, if the archive is on an offline drive, this won't happen until that drive is plugged back in.
"""]]

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.
"""]]

13
doc/forum/archival_and_multiple_users/comment_4_b89a56a5f1cd641f87925c7a5f74bcec._comment Normal file
View file

@ -0,0 +1,13 @@
[[!comment format=mdwn
username="http://joeyh.name/"
ip="2001:4978:f:21a::2"
subject="comment 4"
date="2013-07-25T19:23:30Z"
content="""
Moving files shouldn't jepardize anything. If a user makes a change they shouldn't have made, it can be reverted.
If you have the archive drive available locally you can set your repository to manual mode and just use `git annex get` on content you want. Or you could set it to be a backup repository and the assistant would get all content.
Or write a custom [[preferred_content]] expression for your repository to make it want files in `archive/stillusing/`
"""]]