From cb54ec04c5bc5b6eb365b8c6d41cec887a934fa7 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Tue, 21 Oct 2014 20:20:25 +0000 Subject: [PATCH] Added a comment --- ...ent_2_7316cba69b9dc0415fea1389238edf25._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/bugs/present_files__47__directories_are_dropped_after_a_sync/comment_2_7316cba69b9dc0415fea1389238edf25._comment diff --git a/doc/bugs/present_files__47__directories_are_dropped_after_a_sync/comment_2_7316cba69b9dc0415fea1389238edf25._comment b/doc/bugs/present_files__47__directories_are_dropped_after_a_sync/comment_2_7316cba69b9dc0415fea1389238edf25._comment new file mode 100644 index 0000000000..194f7a3d9f --- /dev/null +++ b/doc/bugs/present_files__47__directories_are_dropped_after_a_sync/comment_2_7316cba69b9dc0415fea1389238edf25._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.96" + subject="comment 2" + date="2014-10-21T20:20:25Z" + content=""" +The problem is that there's no way for preferred content expressions to specify that a file is wanted just because some old version of the file is (or was) present. + +It's not clear to me how that could be added to the preferred content expressions in an efficient way. + +It might be possible to hack `git annex sync --content` and the assistant to look at incoming merges, and queue downloads of newer versions of files before merging. + +Also being discussed at . +"""]]