diff options
| -rw-r--r-- | debian/changelog | 6 | ||||
| -rw-r--r-- | doc/bugs/Amazon_S3_storage_hosted_in_Frankfurt_not_usable.mdwn | 2 | ||||
| -rw-r--r-- | doc/design/balanced_preferred_content.mdwn | 14 | ||||
| -rw-r--r-- | doc/todo/get_--incomplete.mdwn | 6 | ||||
| -rw-r--r-- | git-annex.cabal | 2 |
5 files changed, 27 insertions, 3 deletions
diff --git a/debian/changelog b/debian/changelog index 4508ab21a..8fdf5ef7e 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,4 +1,4 @@ -git-annex (5.20150523) UNRELEASED; urgency=medium +git-annex (5.20150528) unstable; urgency=medium * fromkey, registerurl: Allow urls to be specified instead of keys, and generate URL keys. @@ -11,8 +11,10 @@ git-annex (5.20150523) UNRELEASED; urgency=medium * fsck: When checksumming a file fails due to a hardware fault, the file is now moved to the bad directory, and the fsck proceeds. Before, the fsck immediately failed. + * Linux standalone: The webapp was not built in the previous release, + this release fixes that oversight. - -- Joey Hess <id@joeyh.name> Fri, 22 May 2015 22:23:32 -0400 + -- Joey Hess <id@joeyh.name> Thu, 28 May 2015 10:48:03 -0400 git-annex (5.20150522) unstable; urgency=medium diff --git a/doc/bugs/Amazon_S3_storage_hosted_in_Frankfurt_not_usable.mdwn b/doc/bugs/Amazon_S3_storage_hosted_in_Frankfurt_not_usable.mdwn index 17b10b575..999d648b8 100644 --- a/doc/bugs/Amazon_S3_storage_hosted_in_Frankfurt_not_usable.mdwn +++ b/doc/bugs/Amazon_S3_storage_hosted_in_Frankfurt_not_usable.mdwn @@ -15,3 +15,5 @@ The request signature we calculated does not match the signature you provided. C """]] I have not tried other hosting locations but I assume it has to do with the location which is not listed in the dropdown-list. + +> [[done]]; etooold --[[Joey]] diff --git a/doc/design/balanced_preferred_content.mdwn b/doc/design/balanced_preferred_content.mdwn index 1f00a0339..adc373183 100644 --- a/doc/design/balanced_preferred_content.mdwn +++ b/doc/design/balanced_preferred_content.mdwn @@ -64,3 +64,17 @@ This does not really avoid the limitations above, but having more repos that want each file will reduce the chances that no repo will be able to take a given file. In the [[iabackup]] scenario, new clients will just be assigned until all the files reach the desired level or replication. + +However.. Imagine there are 9 repos, all full, and some files have not +reached desired level of replication. Seems like adding 1 more repo will make +only 3 in 10 files be wanted by that new repo. Even if the repo has space +for all the files, it won't be sufficient, and more repos would need to be +added. + +One way to avoid this problem would be if the preferred content was only +used for the initial distribution of files to a repo. If the repo has +gotten all the files it wants, it could make a second pass and +opportunisticly get files it doesn't want but that it has space for +and that don't have enough copies yet. +Although this gets back to the original problem of multiple repos racing +downloads and files getting more than the desired number of copies. diff --git a/doc/todo/get_--incomplete.mdwn b/doc/todo/get_--incomplete.mdwn new file mode 100644 index 000000000..5b013cb36 --- /dev/null +++ b/doc/todo/get_--incomplete.mdwn @@ -0,0 +1,6 @@ +Use case: Resuming downloads that are incomplete (files in .git/annex/tmp), +without needing to remember the original get command(s) that started the +download. + +`git annex get --incomplete` could do this. (With or without --from to +specify which remote to get from.) --[[Joey]] diff --git a/git-annex.cabal b/git-annex.cabal index 25b1b6438..fa255d4d5 100644 --- a/git-annex.cabal +++ b/git-annex.cabal @@ -1,5 +1,5 @@ Name: git-annex -Version: 5.20150522 +Version: 5.20150528 Cabal-Version: >= 1.8 License: GPL-3 Maintainer: Joey Hess <id@joeyh.name> |