summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar http://id.clacke.se/ <clacke@web>2013-12-17 21:59:28 +0000
committerGravatar admin <admin@branchable.com>2013-12-17 21:59:28 +0000
commit726a90773078d55a6039e7f538d2a0d971674c8d (patch)
tree1d3b6cd47dd9db094aa55a6ea0c9825538f7528c
parent833f07c4756988bc714bd4773f1ffd356bb989c5 (diff)
mention `migrate` and make what is hopefully some clarification
-rw-r--r--doc/bugs/feature_request:_addhash.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/bugs/feature_request:_addhash.mdwn b/doc/bugs/feature_request:_addhash.mdwn
index abafa5289..78e132d0a 100644
--- a/doc/bugs/feature_request:_addhash.mdwn
+++ b/doc/bugs/feature_request:_addhash.mdwn
@@ -13,7 +13,7 @@ I have a big repo of files I have added using `addurl --fast`. I download the fi
### Workaround
-In both these cases, what I can do is unlock (maybe?) or unannex (definitely) all of the files, and then re-add them using the new hash. In both cases this means I now risk having duplicates in various clones of the repo, and would have to clean them up with `drop-unused` -- after first having re-copied them from a repo that has them under the new hash. I also lose the continuity of the history of that object.
+In both these cases, what I can do is <del>unlock (maybe?) or unannex (definitely) all of the files, and then re-add them using the new hash</del> use `migrate` to relink the files using the new scheme. In both use cases this means I now risk having duplicates in various clones of the repo, and would have to clean them up with `drop-unused` -- after first having re-copied them from a repo that has them under the new hash or `migrate`d them in each clone using the pre-migration commit; Either way is problematic for special remotes, in particular glacier. I also lose the continuity of the history of that object.
In use case 2 I also lose the URLs of the files and would have to re-add them using `addurl`.