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 2012-11-07 17:36:41 -04:00
commit 17fd1bd919
3 changed files with 32 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

16
doc/bugs/migrated_files_not_showing_up_in_unused_list/comment_1_2cfbf6693b051c758fe5efa5ee885829._comment Normal file
View file

@ -0,0 +1,16 @@
[[!comment format=mdwn
username="http://joeyh.name/"
ip="4.152.108.27"
subject="comment 1"
date="2012-11-07T19:02:45Z"
content="""
Notice where it says:
> (checking master...) (checking rose/master...) (checking x200s/master...)
AFAICS, every one of those branches still refers to the migrated keys. For one thing, `git annex migrate` makes changes, but it doesn't commit them to master. And then you need to wait until the other remote are updated to.
Also, there's not really any point in worrying about getting rid of migrated keys, since `git-annex migrate` hard links the new key to the old key, so the old ones don't take up any additional disk space.
In other words: This should take care of itself as you continue to use the repository.
"""]]

8
doc/forum/Unknown_remote_type_S3/comment_1_2aea2cd51286c809427d16519606cd37._comment Normal file
View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="http://joeyh.name/"
ip="4.152.108.27"
subject="comment 1"
date="2012-11-07T18:57:17Z"
content="""
It's possible to build git-annex without S3 support. I think a few Linux distros ship it this way due to not having all the necessary haskell libraries.
"""]]

8
doc/forum/Unknown_remote_type_S3/comment_2_06f775062cd30767979fe56bcb3cf7bf._comment Normal file
View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="annexuser"
ip="24.16.193.140"
subject="comment 2"
date="2012-11-07T20:12:27Z"
content="""
That was the issue. Thank you!
"""]]