From b196df9fce9c699f3b9c1e032e3a3017a269295b Mon Sep 17 00:00:00 2001 From: "vrs+annex@ea5fa24dbb279be61a8e50adb638bf8366300717" Date: Sat, 17 Mar 2018 18:26:27 +0000 Subject: [PATCH] --- ..._older_file_versions_after_unlock+add.mdwn | 22 +++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 doc/bugs/if_annex.genmetadata_is_true__44___modification_metadata_is_imported_from_older_file_versions_after_unlock+add.mdwn diff --git a/doc/bugs/if_annex.genmetadata_is_true__44___modification_metadata_is_imported_from_older_file_versions_after_unlock+add.mdwn b/doc/bugs/if_annex.genmetadata_is_true__44___modification_metadata_is_imported_from_older_file_versions_after_unlock+add.mdwn new file mode 100644 index 0000000000..efd4ad492b --- /dev/null +++ b/doc/bugs/if_annex.genmetadata_is_true__44___modification_metadata_is_imported_from_older_file_versions_after_unlock+add.mdwn @@ -0,0 +1,22 @@ +### Please describe the problem. +I've enabled annex.genmetadata to track file modification time. When I unlock, edit and re-add a file, annex imports the modification data from its previous life instead of using the edited (or unedited) file's. + +Annex should always use the added file's mtime as modification time, even if there is conflicting pre-existing metadata. Even better would be if it stored modification time per-object, not worktree file. + +### What steps will reproduce the problem? +```git init testannex; +cd testannex; +git annex init; +git config annex.genmetadata true; +touch bar; +git annex add bar; +git annex sync; +git annex unlock bar; +vim bar; +git annex add bar``` + +output: `Copied metadata from old version of bar to new version. If you don't want this copied metadata, run: git annex metadata --remove-all bar` + +### What version of git-annex are you using? On what operating system? +6.20180227, various Linuxes. +