diff options
| author |  Joey Hess <joey@kitenet.net> | 2011-02-01 21:04:43 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2011-02-01 21:04:43 -0400 |
| commit | 9aecf4110afb2fb1f6b10a9a9234ad0afafda56e (patch) | |
| tree | 837743b7dc911ef39c47afa41ebe7356fb792c8e | |
| parent | ed089c22554ca5b3cd8c8f532db4a9fcc65385d1 (diff) | |
followup
| -rw-r--r-- | doc/bugs/unannex_vs_unlock_hook_confusion.mdwn | 6 |
1 files changed, 5 insertions, 1 deletions
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]] |