comment

diff --git a/doc/forum/How_are_people_handling_the_v8_repo_upgrade__63__/comment_2_23cfa4b9abe96e4477f06c5271b706b2._comment b/doc/forum/How_are_people_handling_the_v8_repo_upgrade__63__/comment_2_23cfa4b9abe96e4477f06c5271b706b2._comment
new file mode 100644 (file)
index 0000000..6465d7e
--- /dev/null
+++ b/doc/forum/How_are_people_handling_the_v8_repo_upgrade__63__/comment_2_23cfa4b9abe96e4477f06c5271b706b2._comment
@@ -0,0 +1,23 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 2"""
+ date="2020-10-27T18:23:30Z"
+ content="""
+A git-annex repo consisting of annex symlinks (locked files) can be cloned
+and used on machines running git-annex versions between 2 and 8. (Any
+version from the past 9 years.) It's the same information stored in git.
+
+If you choose to commit unlocked files to the repo, those files will only
+work when using git-annex 7 or 8. But that's optional and you can also just
+re-lock the files to regain compatability all the way back to version 2.
+
+So, no, you do not need to worry about git-annex sync breaking something.
+
+And, git-annex 8 on one machine can talk to git-annex 7 (or any version
+really) on another machine, no problem.
+
+Now, if you have a repo that you are physically moving around between
+machines, on USB for example, then the machines all need have to have
+a git-annex version installed that's compatible with the annex.version
+of the repo.
+"""]]