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 2014-02-20 18:48:10 -04:00
commit d51d0a344f
8 changed files with 91 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
doc/bugs/Numcopies_not_checked_when_running_with_--all/comment_1_63af5a11c3ae370433c4bf84de097414._comment Normal file
View file

@ -0,0 +1,9 @@
[[!comment format=mdwn
username="stp"
ip="84.56.21.11"
subject="Some suggestions"
date="2014-02-20T21:22:21Z"
content="""
So I think it should at least for --all look at the global numcopies setting. As this could be essential to prevent data-loss.
I agree that special working tree related numcopies don't need to be included.
"""]]

14
doc/bugs/fsck_giving_false_checking_information/comment_3_be4d0fec56c29cf978ef7d1715eaa516._comment Normal file
View file

@ -0,0 +1,14 @@
[[!comment format=mdwn
username="stp"
ip="84.56.21.11"
subject="Great improvements"
date="2014-02-20T21:20:15Z"
content="""
Thanks for clearing it up. It is still a bit confusing that you have to differentiate on the second run. (using --more) I probably view it as inconvenient as it make me have to remember the first and second time of running a command. I think it would be cleaner to have \"--incremental\" always skipping files and \"--incremental restart\" start from the beginning.
Ah great yeah they are different functions and should therefore not interfere. (fsck --fast --incremental)
Great that the checksum is back in and yeah I agree that it isn't really needed in the add command.
"""]]

14
doc/bugs/git_annex_sync_--content_not_syncing_all_objects/comment_2_70804d50b07630fadfc029a22173c5a0._comment Normal file
View file

@ -0,0 +1,14 @@
[[!comment format=mdwn
username="stp"
ip="84.56.21.11"
subject="Some ideas for content sync"
date="2014-02-20T21:18:30Z"
content="""
I agree that it is a tricky situation. The main issue I have is that archive preferred content expressions indicates that all versions are transferred, but when you (worst case) migrate full archives to other disks and just use git annex sync --content, you would loose all objects.
I like the idea of --content --all as this would be consistent with other commands such as fsck for example.
Still it seems with preferred content expressions only applying to working tree data that it would still miss \"copies=backup:2\" for example and only use working tree files. Which is misleading and could lead to dataloss in my opinion.
So the best would probably be to let preferred content for number of copies at least work on all objects, either per default or when \"git annex sync --content --all\" is used. You wouldn't run that on usual repos, but definitely on backup, archive or similar repos.
"""]]

8
doc/devblog/day_-4__forgetting/comment_4_812b630df01ac35254e3c4e677554e2b._comment Normal file
View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="stp"
ip="84.56.21.11"
subject="comment 4"
date="2014-02-20T21:07:41Z"
content="""
Yeah true if I remove symlinks from the history (as I understand your suggestion) it would work. I just wanted to suggest that it could be something useful for the git annex forget function as it already cleans out old dead repos and other things.
"""]]

8
doc/devblog/day_-4__forgetting/comment_5_a9670eca2aff9ad5f04412a8d8b6df6a._comment Normal file
View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="http://joeyh.name/"
ip="209.250.56.172"
subject="comment 5"
date="2014-02-20T21:14:21Z"
content="""
You don't need to delete them from the history, just from the branch you're running `git annex fsck` in.
"""]]

9
doc/devblog/day_-4__forgetting/comment_6_4f87e2ab119f3cd81266159f02952188._comment Normal file
View file

@ -0,0 +1,9 @@
[[!comment format=mdwn
username="stp"
ip="84.56.21.11"
subject="comment 6"
date="2014-02-20T22:19:12Z"
content="""
As discussed on irc.
Fsck --all does check more then the working tree and therefore for fsck to not complain this would be a worthy feature to be added. (git annex forget $key)
"""]]

8
doc/devblog/day_119__catching_up/comment_1_8aa413e75cab411b0aec254f0f33ebb9._comment Normal file
View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="https://www.google.com/accounts/o8/id?id=AItOawlJEI45rGczFAnuM7gRSj4C6s9AS9yPZDc"
nickname="Kevin"
subject="Neat!"
date="2014-02-20T21:59:05Z"
content="""
When the [[metadata design|day_112__metadata_design]] stuff appeared on the blog I didn't understand what you meant by automatically creating new tree layouts. I'm really liking these views and can already imagine how useful it would be to tag my photos by person/place/time. This is awesome! Keep up the good work.
"""]]

21
doc/tips/using_Amazon_Glacier/comment_4_e6ac76b0c20285f4f96b3d0975e8ac66._comment Normal file
View file

@ -0,0 +1,21 @@
[[!comment format=mdwn
username="http://grossmeier.net/"
nickname="greg"
subject="comment 4"
date="2014-02-20T22:04:58Z"
content="""
Along with stupid python problems which are now fixed (all my fault, and hopefully didn't cause more noise here than needed), the only thing that didn't go as stated was:
[[!format sh \"\"\"
greg@x200s:~/Photos$ git-annex enableremote glacier
enableremote glacier
Set both AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY to use glacier
git-annex: Failed creating glacier vault.
greg@x200s:~/Photos$ AWS_ACCESS_KEY_ID=lolno AWS_SECRET_ACCESS_KEY=lolno git-annex enableremote glacier
enableremote glacier ok
(Recording state in git...)
greg@x200s:~/Photos$
\"\"\"]]
The guide says that info is sync'd.
"""]]