aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar chocolate.camera@ec2ecab153906be21ac5f36652c33786ad0e0b60 <chocolatecamera@web>2017-07-10 10:17:34 +0000
committerGravatar admin <admin@branchable.com>2017-07-10 10:17:34 +0000
commit39c4fb26404ce89be4287f55a6295ca128427da7 (patch)
tree8bd3f9b4fff6193f8678f6fb221f5937b5fff9ee
parent20e3eb7f541afcca454272440e305fa6822488d3 (diff)
How to use git-annex for content on external drives only?
-rw-r--r--doc/forum/Workflow_for_using_git-annex_only_on_external_drives.mdwn8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/forum/Workflow_for_using_git-annex_only_on_external_drives.mdwn b/doc/forum/Workflow_for_using_git-annex_only_on_external_drives.mdwn
new file mode 100644
index 000000000..734be10ea
--- /dev/null
+++ b/doc/forum/Workflow_for_using_git-annex_only_on_external_drives.mdwn
@@ -0,0 +1,8 @@
+I am starting to use annex and feel a bit overwhelmed. I would appreciate guidance on this use case.
+
+1. Content must exist on multiple external drives only. I do not want those files in my internal HDD.
+2. Not all drives will have all files. Probably none will. Drives might be smaller than the full set.
+3. I should always have two copies of each file somewhere (and be warned if not).
+3. Some files already exist in some drives I intend to use annex with in this way. When setting annex in them, I had rather avoid having to transfer in files from another set up drive if those files already exist in the new drive.
+4. Some drives will necessarily be using FAT32.
+5. I will be adding new content over time.