diff options
| author |  Joey Hess <joey@kitenet.net> | 2014-07-23 17:56:26 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2014-07-23 17:56:26 -0400 |
| commit | e9e2ce62f1118229c98c44b20c57745afd1ebb9f (patch) | |
| tree | 5a443aaf5143cf82e2fe3c65a0a926da3b2f0a49 | |
| parent | d0a0145fc19cd1857fbe544ca53c9cf397424ce1 (diff) | |
link
| -rw-r--r-- | doc/design/assistant/chunks.mdwn | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/design/assistant/chunks.mdwn b/doc/design/assistant/chunks.mdwn index 49cffac81..224c719f8 100644 --- a/doc/design/assistant/chunks.mdwn +++ b/doc/design/assistant/chunks.mdwn @@ -29,7 +29,7 @@ Every special remote should support chunking. (It does not make sense to support it for git remotes, but gcrypt remotes should support it.) S3 remotes should chunk by default, because the current S3 backend fails -for files past a certian size. See [[bugs/]] +for files past a certian size. See [[bugs/Truncated_file_transferred_via_S3]]. The size of chunks, as well as whether any chunking is done, should be configurable on the fly without invalidating data already stored in the |