summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar gernot <gernot@web>2014-12-30 17:46:02 +0000
committerGravatar admin <admin@branchable.com>2014-12-30 17:46:02 +0000
commit28a21d976886a049ef9d15bb4508cce823b12a8b (patch)
tree9cb79e9b7399d3c33f30ad885ea34925f0e43a9b
parent80d4481bf8ffed3c196c36d0d478c24b0cfd8cec (diff)
-rw-r--r--doc/forum/Disk_usage_during___96__import__96__.mdwn5
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/forum/Disk_usage_during___96__import__96__.mdwn b/doc/forum/Disk_usage_during___96__import__96__.mdwn
new file mode 100644
index 000000000..9ece26e33
--- /dev/null
+++ b/doc/forum/Disk_usage_during___96__import__96__.mdwn
@@ -0,0 +1,5 @@
+Does `git-annex import` move data to the working directory before moving it to `.git/annex/objects`?
+
+The reason I'm asking is that I use the split SSD/HDD setup with some annexes, i.e., everything resides on an SSD except for the git-annex objects directory.
+
+If git-annex wrote imported data to the working directoy (on the SSD) first and moved it to the objects directory (on the HDD) later, it would cause lots of unnecessary writes to the SSD.