diff options
| author |  andy <andy@web> | 2016-10-29 22:31:02 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2016-10-29 22:31:02 +0000 |
| commit | 8540d4927ecf2f90160b960bb4504407b672bd25 (patch) | |
| tree | d8256b2dbfd80c2d08a4dbfb505f8f4f76479027 | |
| parent | df505ebd58c64d3a3aea955264d07cc14604a4d5 (diff) | |
| -rw-r--r-- | doc/forum/version_5_repo_with_version_6_repo.mdwn | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/doc/forum/version_5_repo_with_version_6_repo.mdwn b/doc/forum/version_5_repo_with_version_6_repo.mdwn new file mode 100644 index 000000000..1bf0b8eb3 --- /dev/null +++ b/doc/forum/version_5_repo_with_version_6_repo.mdwn @@ -0,0 +1 @@ +I've found that when a file is unlocked in a v6 repo, syncing with a v5 repo causes the file in the v5 repo to be a symlink-replacement file (the file contents are, e.g., /annex/objects/SHA256E-s10--114811b0b8998cb9853a5379598021410feddf69bb2ee7b7145d052a7e9b5d45). I'm wondering if this is a bug, or just something that users should be aware of. |