From 9aecf4110afb2fb1f6b10a9a9234ad0afafda56e Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 1 Feb 2011 21:04:43 -0400 Subject: followup --- doc/bugs/unannex_vs_unlock_hook_confusion.mdwn | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/doc/bugs/unannex_vs_unlock_hook_confusion.mdwn b/doc/bugs/unannex_vs_unlock_hook_confusion.mdwn index 8a6330377..7e4a9f291 100644 --- a/doc/bugs/unannex_vs_unlock_hook_confusion.mdwn +++ b/doc/bugs/unannex_vs_unlock_hook_confusion.mdwn @@ -6,4 +6,8 @@ now committing a changed version, and the right thing to do there is to add the new content to the annex and update the symlink accordingly. Can we tell the difference between an unannexed file that has yet to be committed -and an unlocked file? --[[Joey|| +and has been re-added as a normal file, vs an unlocked file? --[[Joey|| + +> Hmm, not really. An unannexed file's content will have been dropped from +> the backend, but that's about the only difference. Perhaps unannex should +> just commit the removal of the file itself? --[[Joey]] -- cgit v1.2.3