diff options
| author |  Joey Hess <joey@kitenet.net> | 2011-03-28 08:52:42 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2011-03-28 08:52:42 -0400 |
| commit | d2ed1b3a99da45ae25e84cbc832693442bab7de6 (patch) | |
| tree | 0fef430b74c62a5a18259d107e58227ce4032a73 /doc/bugs/backend_version_upgrade_leaves_repo_unusable.mdwn | |
| parent | 02601c6b9f2129e80323abea5ad76bf64c27b574 (diff) | |
second thought
Diffstat (limited to 'doc/bugs/backend_version_upgrade_leaves_repo_unusable.mdwn')
| -rw-r--r-- | doc/bugs/backend_version_upgrade_leaves_repo_unusable.mdwn | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/bugs/backend_version_upgrade_leaves_repo_unusable.mdwn b/doc/bugs/backend_version_upgrade_leaves_repo_unusable.mdwn index 964a176bd..7bbd02364 100644 --- a/doc/bugs/backend_version_upgrade_leaves_repo_unusable.mdwn +++ b/doc/bugs/backend_version_upgrade_leaves_repo_unusable.mdwn @@ -56,4 +56,7 @@ Running the copy job again, I am still getting the same error as above (as expec >>> it even makes sense to fix the crash. I should probably focus >>> on fixing what let these mixed keys be created by the mixed-version >>> copy. +>>> +>>> On second thought, you shouldn't delete anything. I'll simply +>>> make the v2 upgrade detect and work around this bug. >>> --[[Joey]] |