diff options
| author |  Joey Hess <joey@kitenet.net> | 2011-05-17 12:18:50 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2011-05-17 12:18:50 -0400 |
| commit | f664a2538a848d204922de908fac9add7c1db0fe (patch) | |
| tree | fc4f6574cb73b98085694efcfb0654ada1b4fe26 | |
| parent | ebfa50b72959de4c4e917771c57b0efcea98e55b (diff) | |
fix
| -rw-r--r-- | doc/todo/tahoe_lfs_for_reals.mdwn | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/todo/tahoe_lfs_for_reals.mdwn b/doc/todo/tahoe_lfs_for_reals.mdwn index 053a763d7..4e0bf2fb1 100644 --- a/doc/todo/tahoe_lfs_for_reals.mdwn +++ b/doc/todo/tahoe_lfs_for_reals.mdwn @@ -5,7 +5,7 @@ hash subdirectories in Tahoe is expensive. Instead it would be good to use it as a key/value store directly. The catch is that doing so involves sending the content to Tahoe, and getting back a key identifier. -This would be fairly easy to do as a [[backend]], which can assign its +This would be fairly easy to do as a [[backend|backends]], which can assign its own key names (although typically done before data is stored in it), but a tahoe-lafs special remote would be more flexible. |