summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2014-12-30 14:10:35 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2014-12-30 14:10:35 -0400
commitc39a0761967eb0c242f9a08d9c617ff435788a3d (patch)
tree51e0895ee0be11a7fe6aa286cbccdce67ab3e038
parent097539fb6bfe605ef5d57fb91b901cc11352562a (diff)
parent28a21d976886a049ef9d15bb4508cce823b12a8b (diff)
Merge branch 'master' of ssh://git-annex.branchable.com
-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.