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=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U 2014-03-10 17:15:54 +00:00 • committed by admin
parent f8eea14722
commit 0c595a42ae
1 changed files with 23 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

23
doc/todo/required_content/comment_1_42620a3c958666be2a0d5f5b8eadf7b4._comment Normal file
View file

@ -0,0 +1,23 @@
[[!comment format=mdwn
username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
nickname="Richard"
subject="comment 1"
date="2014-03-10T17:15:54Z"
content="""
To give a specific example of what I want to do:
I have a bunch of repos
* A, Machine1 -- anchor repository and sometimes used to add new content
* B, Machine2 -- anchor repository, offsite
* C, External1 -- anchor repository, stored off-site
* D, Laptop -- transient repo to carry data around and to add new content
* E, USB1 -- transient, travel backups
* F, USB2 -- transient, travel backups
A-C should get _all_ data. A-F trust A-C to always retain all data, online checks for availability are not needed because A-C run frequent fsck. Ideally, `git annex drop` should be no-op in A-C.
D-F should retain data as long as it's not been saved in _all_ of A-C. As soon as A-C have copies, `git annex drop` in D-F should drop that content; before that, they _must not_ drop said content.
Richard
"""]]