summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar https://www.google.com/accounts/o8/id?id=AItOawmTNrhkVQ26GBLaLD5-zNuEiR8syTj4mI8 <Juan@web>2013-08-23 14:51:26 +0000
committerGravatar admin <admin@branchable.com>2013-08-23 14:51:26 +0000
commitd77245f7501ab7f8bfdffbd5b5cd56c880a4f24a (patch)
treec59e2d6de22c820576e7feeac66a19cae626947c
parentd3f3a1d746e922adb29a1d7817dbb3c47272d285 (diff)
-rw-r--r--doc/forum/correct_way_to_add_two_preexisting_datasets.mdwn3
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/forum/correct_way_to_add_two_preexisting_datasets.mdwn b/doc/forum/correct_way_to_add_two_preexisting_datasets.mdwn
index 35ed5b665..66de6494f 100644
--- a/doc/forum/correct_way_to_add_two_preexisting_datasets.mdwn
+++ b/doc/forum/correct_way_to_add_two_preexisting_datasets.mdwn
@@ -1,10 +1,13 @@
I've been syncronizing my data since long time, mainly using rsync or unison. Thus I had two 3.5Gb datasets set1 (usb drive, hfs+ partition) and set2 (hdd, ext4 ubuntu 13.04 box) which differed only in 50Mb (new on set1 ). This was double checked using diff -r before doing anything.
+
I created a git annex repo in direct mode for set2 from command line, and after that I let the assistant scan it.
After that created the repo for set1 and added it to the assistant. I think here comes my mistake (I think).
+
Instead of keeping them apart, at told assistant to sync with set2.
Why I think this was a mistake? Because set2 was indexed and set1 no, and I'm seeing a lot of file moving a copying, which in my humble opinion should not happen.
What I expected it only the difference to be transferred from set1 to set2.
What it seems to be doing is moving away all content in set1, and copying it back from set2. I think it will end correctly, but with a lot of unnecessary and risky operations.
+
I think I should have independently added both datasets, let them be scanned and then connect to each other.
So, now the questions:
1. Is that the correct way to proceed?