diff options
author | susetux@ed6f4e20192c3eae018e1fc6442bf993d41b3848 <susetux@web> | 2016-03-13 11:20:49 +0000 |
---|---|---|
committer | admin <admin@branchable.com> | 2016-03-13 11:20:49 +0000 |
commit | c2977739607a903ecd65eaefdf9dbb8c60f18b9d (patch) | |
tree | cb243849462001c555269d970ffbb039aefa39fa /doc | |
parent | 1387bfc732edc1c6c69c1d985ca42b1bff51797c (diff) |
Diffstat (limited to 'doc')
-rw-r--r-- | doc/forum/converting_a_v5_repo_to_an_always_unlocked_v6_repo.mdwn | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/doc/forum/converting_a_v5_repo_to_an_always_unlocked_v6_repo.mdwn b/doc/forum/converting_a_v5_repo_to_an_always_unlocked_v6_repo.mdwn index 7c42094fa..11ff6116b 100644 --- a/doc/forum/converting_a_v5_repo_to_an_always_unlocked_v6_repo.mdwn +++ b/doc/forum/converting_a_v5_repo_to_an_always_unlocked_v6_repo.mdwn @@ -19,8 +19,7 @@ Then I try to commit the changes with: The process seems to take and incredibly long time (several hours) and then ends up running out of space. I check the repository with "du -sh" and it's almost double the size. Is there a reason for this? Is there a way to avoid this duplication of data. Shouldn't annex.thin do the trick? -Should I not have done the sync thing? (I need to sync with other repos too after the migration is done) -Is there a correct way to migrate my repo to an always unlocked one which won't require hours of time and take all that disk space? +Is there a correct and faster way to migrate my repo to an always unlocked one which won't require hours of time and take all that disk space? thanks a lot, daniel |