From 3868a65663231b929a1c09b02185e85dc70e59e5 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U" Date: Sat, 29 Oct 2011 17:07:44 +0000 Subject: [PATCH] --- doc/bugs/uninit_does_not_work_in_old_repos.mdwn | 2 ++ 1 file changed, 2 insertions(+) diff --git a/doc/bugs/uninit_does_not_work_in_old_repos.mdwn b/doc/bugs/uninit_does_not_work_in_old_repos.mdwn index 1e1b1fec73..0e5175abe3 100644 --- a/doc/bugs/uninit_does_not_work_in_old_repos.mdwn +++ b/doc/bugs/uninit_does_not_work_in_old_repos.mdwn @@ -13,3 +13,5 @@ If the repo happens to be broken, this essentially locks in data. > And it depends on the object directory layout, which has changed between > versions. So supporting old versions in this code would complicate it > quite a lot. I don't want to go there. --[[Joey]] + +>>Requiring a version upgrade for unannex is fine. Yet, I see a problem when a git repo is broken; you are stuck without being able to uninit. In this case an uninit that does nothing but undo the symlinking would be useful. -- Richard