diff options
| author |  Joey Hess <joey@kitenet.net> | 2012-10-31 13:33:14 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2012-10-31 13:33:14 -0400 |
| commit | 71365330365c5c0e4032fecb692ac47631bfad47 (patch) | |
| tree | 0a15156f7a12d3010e6d3927c573491211f74795 | |
| parent | 26f158c86b678c16f280b3bc5c6b96c183876a16 (diff) | |
close
| -rw-r--r-- | doc/bugs/__34__drop__34___deletes_all_files_with_identical_content.mdwn | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/bugs/__34__drop__34___deletes_all_files_with_identical_content.mdwn b/doc/bugs/__34__drop__34___deletes_all_files_with_identical_content.mdwn index 45761fb04..bdf48760c 100644 --- a/doc/bugs/__34__drop__34___deletes_all_files_with_identical_content.mdwn +++ b/doc/bugs/__34__drop__34___deletes_all_files_with_identical_content.mdwn @@ -44,3 +44,6 @@ Consider the following variation of the above example and assume, that "drop" do --> cat: fileB: No such file or directory Here again, the problem is, that the user would probably (correct me if I am wrong) expect that the fileB still exists, because removing a file and checking it out again is expected to not mess with the annex contents (?). He does not know, that the "annex frop fileA" actually drop fileB's contents, because there was no additional file linking to it. It effectively performed a "git annex dropunused". + +> We seem to have agreed this is reasonable behavior, and a doc change was done. +> Do feel free to suggest other doc changes.. [[done]] --[[Joey]] |