diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2017-12-11 13:09:28 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2017-12-11 13:09:28 -0400 |
| commit | cfb747652dff98321d66dc162edc473ad01afd9a (patch) | |
| tree | 6a23fc9ecc6b7e48db74dfd9932e018ab9eaafe1 | |
| parent | 1a454dc9882737120f7fafe3c2a0bac97ea67433 (diff) | |
followup and closd
| -rw-r--r-- | doc/bugs/issue_with_syncing_between_v5_and_v6_repos.mdwn | 2 | ||||
| -rw-r--r-- | doc/bugs/issue_with_syncing_between_v5_and_v6_repos/comment_1_4c3468a17c454cb344b3a944c0f71889._comment | 27 |
2 files changed, 29 insertions, 0 deletions
diff --git a/doc/bugs/issue_with_syncing_between_v5_and_v6_repos.mdwn b/doc/bugs/issue_with_syncing_between_v5_and_v6_repos.mdwn index c4a302dab..f0ee4ba58 100644 --- a/doc/bugs/issue_with_syncing_between_v5_and_v6_repos.mdwn +++ b/doc/bugs/issue_with_syncing_between_v5_and_v6_repos.mdwn @@ -108,3 +108,5 @@ $ git annex upgrade ### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders) Yes + +> I don't consider this a bug, so [[done]] --[[Joey]] diff --git a/doc/bugs/issue_with_syncing_between_v5_and_v6_repos/comment_1_4c3468a17c454cb344b3a944c0f71889._comment b/doc/bugs/issue_with_syncing_between_v5_and_v6_repos/comment_1_4c3468a17c454cb344b3a944c0f71889._comment new file mode 100644 index 000000000..9db9c27c4 --- /dev/null +++ b/doc/bugs/issue_with_syncing_between_v5_and_v6_repos/comment_1_4c3468a17c454cb344b3a944c0f71889._comment @@ -0,0 +1,27 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2017-12-11T16:59:52Z" + content=""" +The problem is much simpler than that: Files that are unlocked in v6 +repositories are not treated as annexed files at all in v5 repositories. +You cannot `git annex get` them or anything. + +So, the simpler reproduction recipe is to `git add` a file to a v6 +repository and then in a v5 clone, `git annex get` and it won't say +anything, because that's not an annexed file as far as it's concerned. + +It's also very easy to deal with this situation if you've gotten into it -- +all you need to do is `git annex lock` the files in a v6 repository and +commit it, and then the v5 repository will be able to access them. + +A good way to avoid the problem while still using the features of v6 +in your v6 repository is to run `git annex adjust --unlock` in there. +Then commits of unlocked files will automatically be translated to locked +files that are compatible with v5. + +git-annex v5 can't possibly treat v6 unlocked files as annexed files. +It could warn about the problem, but this would complicate it with needing +to check if every non-symlink file is a v6 unlocked file. I don't feel +this problem warrants that complication. +"""]] |