diff options
| -rw-r--r-- | doc/bugs/set_metadata_leaks_from_one___40__staged__41___key_to_another_during_rename_of_file/comment_3_10d6135ad4b0c9706ff7b932323118d3._comment | 21 |
1 files changed, 21 insertions, 0 deletions
diff --git a/doc/bugs/set_metadata_leaks_from_one___40__staged__41___key_to_another_during_rename_of_file/comment_3_10d6135ad4b0c9706ff7b932323118d3._comment b/doc/bugs/set_metadata_leaks_from_one___40__staged__41___key_to_another_during_rename_of_file/comment_3_10d6135ad4b0c9706ff7b932323118d3._comment new file mode 100644 index 000000000..26d2ff01f --- /dev/null +++ b/doc/bugs/set_metadata_leaks_from_one___40__staged__41___key_to_another_during_rename_of_file/comment_3_10d6135ad4b0c9706ff7b932323118d3._comment @@ -0,0 +1,21 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2017-09-26T19:16:29Z" + content=""" +Hmm, if the file was not already in the index, that could be taken to +indicate it was deleted/moved and replaced, rather than being modified, +and so don't copy the metadata. + +But that would make these two sequences have different behavior: + + git rm file; echo foo > file; git annex add file + + echo foo > file; git annex add file + +As well as these two sequences: + + git mv file other; echo foo > file; git annex add file + + cp file other; echo foo > file; git annex add file other +"""]] |