diff options
author | 2014-01-08 20:01:12 -0400 | |
---|---|---|
committer | 2014-01-08 20:01:12 -0400 | |
commit | 414dc44091254a908e14dc9c402bb242f913a29c (patch) | |
tree | 631d37b99281f916e2a3431cb931c221d97efd15 /doc/todo/tahoe_lfs_for_reals.mdwn | |
parent | c44ecb7bb2dc49d5334265389ceae4b0718a9b8d (diff) |
update
Diffstat (limited to 'doc/todo/tahoe_lfs_for_reals.mdwn')
-rw-r--r-- | doc/todo/tahoe_lfs_for_reals.mdwn | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/doc/todo/tahoe_lfs_for_reals.mdwn b/doc/todo/tahoe_lfs_for_reals.mdwn index 9019767eb..e5b4a841d 100644 --- a/doc/todo/tahoe_lfs_for_reals.mdwn +++ b/doc/todo/tahoe_lfs_for_reals.mdwn @@ -10,12 +10,12 @@ own key names (although typically done before data is stored in it), but a tahoe-lafs special remote would be more flexible. To support a special remote, a mapping is needed from git-annex keys to -Tahoe keys. +Tahoe keys, stored in the git-annex branch. -The best place to store this mapping is perhaps as a new field in the -location log: - - date present repo-uuid newfields - -This way, each remote can store its own key-specfic data in the same place -as other key-specific data, with minimal overhead. +> This is now done, however, there are 2 known +> problems: +> +> * tahoe start run unncessarily <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2149> +> * web.port can conflict <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2147> +> +> --[[Joey]] |