From d1f97163ff320c21676528f70213112591ed38dd Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 19 Sep 2017 12:38:07 -0400 Subject: break out separate todo for later --- doc/todo/export.mdwn | 12 ------------ doc/todo/export_paired_rename_innefficenctcy.mdwn | 10 ++++++++++ 2 files changed, 10 insertions(+), 12 deletions(-) create mode 100644 doc/todo/export_paired_rename_innefficenctcy.mdwn diff --git a/doc/todo/export.mdwn b/doc/todo/export.mdwn index 4c707a779..876c54c77 100644 --- a/doc/todo/export.mdwn +++ b/doc/todo/export.mdwn @@ -26,15 +26,3 @@ Work is in progress. Todo list: setting and the "public" repository group. The assistant uses those for IA, which could be replaced with setting up an export tracking branch. - -Low priority: - -* When there are two pairs of duplicate files, and the filenames are - swapped around, the current rename handling renames both dups to a single - temp file, and so the other file in the pair gets re-uploaded - unncessarily. This could be improved. - - Perhaps: Find pairs of renames that swap content between two files. - Run each pair in turn. Then run the current rename code. Although this - still probably misses cases, where eg, content cycles amoung 3 files, and - the same content amoung 3 other files. Is there a general algorythm? diff --git a/doc/todo/export_paired_rename_innefficenctcy.mdwn b/doc/todo/export_paired_rename_innefficenctcy.mdwn new file mode 100644 index 000000000..9284b74d9 --- /dev/null +++ b/doc/todo/export_paired_rename_innefficenctcy.mdwn @@ -0,0 +1,10 @@ +`git annex export` can efficiently handle renames, including renames that swap +content between files. However, when there are two pairs of duplicate files, +and the filenames are swapped around, the current rename handling renames both +dups to a single temp file, and so the other file in the pair gets re-uploaded +unncessarily. This could be improved. + +Perhaps: Find pairs of renames that swap content between two files. +Run each pair in turn. Then run the current rename code. Although this +still probably misses cases, where eg, content cycles amoung 3 files, and +the same content amoung 3 other files. Is there a general algorythm? -- cgit v1.2.3