diff options
| author |  Joey Hess <joey@kitenet.net> | 2014-01-02 20:27:31 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2014-01-02 20:27:31 -0400 |
| commit | eb774f49acd148f04b64f582a9696ede9f9e25fb (patch) | |
| tree | 25b0add38815e9ea77bb196d20e675d4b1a60ec5 /doc/devblog | |
| parent | 7540b736d5e28f8c0644e6c2415c8d2ebf4b5861 (diff) | |
mini-devblog
Diffstat (limited to 'doc/devblog')
| -rw-r--r-- | doc/devblog/day_91__wintry_mix.mdwn | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/devblog/day_91__wintry_mix.mdwn b/doc/devblog/day_91__wintry_mix.mdwn new file mode 100644 index 000000000..bfa9ddd35 --- /dev/null +++ b/doc/devblog/day_91__wintry_mix.mdwn @@ -0,0 +1,11 @@ +Implemented read-only remotes. This may not cover every use case around +wanting to clone a repository and use git-annex without leaking the +existence of your clone back to it, but I think it hits most of them in a +quite easy way, and allows for some potentially interesting stuff like +partitioned networks of git-annex repositories. + +Zooko and I have been talking things over (for rather too long), +and I think have now agreed on a how a more advanced git-annex +Tahoe-LAFS special remote should work. This includes storing the +tahoe file-caps in the git-annex branch. So, I really need to add that +per-special-remote data storage feature I've been thinking about. |