summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2012-03-04 11:02:41 -0400
committerGravatar Joey Hess <joey@kitenet.net>2012-03-04 11:02:41 -0400
commit896fce38472e32e73550b5113f00c9de2147982e (patch)
tree5983281797ea5f5786ab02b9c28daf2df41dabb4
parent013c7ea44170023bf9d8471fb01312a7a3c789cb (diff)
box.com seems to behave better with smaller chunks
Seeing some weird failures in the davfs2 or box.com layer with 100 mb chunks.
-rw-r--r--doc/tips/using_box.com_as_a_special_remote.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/tips/using_box.com_as_a_special_remote.mdwn b/doc/tips/using_box.com_as_a_special_remote.mdwn
index 2e6f73866..b216dd98d 100644
--- a/doc/tips/using_box.com_as_a_special_remote.mdwn
+++ b/doc/tips/using_box.com_as_a_special_remote.mdwn
@@ -37,7 +37,7 @@ Create the special remote, in your git-annex repository.
** This example is non-encrypted; fill in your gpg key ID for a securely
encrypted special remote! **
- git annex initremote box.com type=directory directory=/media/box.com chunksize=100mb encryption=none
+ git annex initremote box.com type=directory directory=/media/box.com chunksize=2mb encryption=none
Now git-annex can copy files to box.com, get files from it, etc, just like
with any other special remote.