summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar cruisevx1@a754a154d8ebc70ae870cdcc7ffa9b2199ff3803 <cruisevx1@web>2016-06-13 02:23:15 +0000
committerGravatar admin <admin@branchable.com>2016-06-13 02:23:15 +0000
commit2c6567d632ea19c38d70dc3bbc288d455b10e148 (patch)
tree0c072357a8d36183cd3b541053634d691c2fd199
parentb1a65160f79de3eb5b0c0c28d081c64c6e028c3b (diff)
-rw-r--r--doc/forum/v5_to_v6_upgrade_strategy.mdwn21
1 files changed, 21 insertions, 0 deletions
diff --git a/doc/forum/v5_to_v6_upgrade_strategy.mdwn b/doc/forum/v5_to_v6_upgrade_strategy.mdwn
new file mode 100644
index 000000000..9a34b01e3
--- /dev/null
+++ b/doc/forum/v5_to_v6_upgrade_strategy.mdwn
@@ -0,0 +1,21 @@
+I have recently jumped into git-annex, and have several TB stored in several remote annexes.
+I am able to sync to clients, and have some understanding of the operations needed to get files back etc.
+
+So far I have used v5 in Ubuntu and Debian 8. I have tried out assistant but will leave this until I better understand how git-annex works. CLI is best for this learning.
+
+I am however concerned re the upgrade path from v5 to v6. I have not been able to find a comprehensive strategy. I have tried git-annex v6 and have upgraded a client repo to v6.
+
+All of my remote repos are v5, and to be honest I am very nervous about touching them.
+
+I do have a test bed where I try out all things before doing so on my 'production' repos. So, I can play, break, redo, in safety.
+
+Any direction as to formulating a game plan for upgrading my whole network of repos, clients, etc would be very much appreciated.
+
+And, if I have missed this, a pointer would be good for sure.
+
+
+Regards,
+
+Stan
+
+While it is obvious to all: this is amazing software. Genius.