diff options
author | 2013-09-13 15:25:53 -0400 | |
---|---|---|
committer | 2013-09-13 15:25:53 -0400 | |
commit | cd7bc814cdf066b361e3b0139be524f00d8b3999 (patch) | |
tree | 5c55143fae673a015e0912a8f7b09fb818c05ea7 /doc/todo/http_git_annex_404_retry.mdwn | |
parent | 72fbf2ccafa838047fed009262fcf47b7cb6ae24 (diff) |
move to todo
Diffstat (limited to 'doc/todo/http_git_annex_404_retry.mdwn')
-rw-r--r-- | doc/todo/http_git_annex_404_retry.mdwn | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/doc/todo/http_git_annex_404_retry.mdwn b/doc/todo/http_git_annex_404_retry.mdwn new file mode 100644 index 000000000..38ab860bb --- /dev/null +++ b/doc/todo/http_git_annex_404_retry.mdwn @@ -0,0 +1,16 @@ +A repository like http://annex.debconf.org/debconf-share/ has a git repo +published via http. When getting files from such a repo, git-annex tries +two urls. One url would be used by a bare repo, and the other by a non-bare +repo. (This is due to the directory hashing change.) Result is every file +download from a non-bare http repo starts with a 404 and then it retries +with the right url. + +Since git-annex already downloads the .git/config to find the uuid of the +http repo, it could also look at it to see if the repo is bare. If not, +set a flag, and try the two urls in reverse order, which would almost +always avoid this 404 problem. + +(The real solution is probably to flag day and get rid of the old-style +directory hashing, but that's been discussed elsewhere.) + +--[[Joey]] |