From 1c2c086d5146741e312380aa7ff95929f39fe3ce Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 6 Jul 2015 15:02:46 -0400 Subject: [PATCH] response --- ...ent_14_80d962f856de7510a437437fc0ca75e1._comment | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 doc/special_remotes/directory/comment_14_80d962f856de7510a437437fc0ca75e1._comment diff --git a/doc/special_remotes/directory/comment_14_80d962f856de7510a437437fc0ca75e1._comment b/doc/special_remotes/directory/comment_14_80d962f856de7510a437437fc0ca75e1._comment new file mode 100644 index 0000000000..2b7acd038d --- /dev/null +++ b/doc/special_remotes/directory/comment_14_80d962f856de7510a437437fc0ca75e1._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 14""" + date="2015-07-06T19:00:43Z" + content=""" +@dmitry, it just so happens that directory special remotes honor the +annex.diskreserve configuration setting. This normally only applies to +the local git repository, and not to remotes, but since directory +special remotes are local annex.diskreserve is also checked for them. + +There's no currently a way to have a different diskreserve setting for +a directory special remote than is used for the local git repository. +"""]]