From 42b381e4b28a429ac751a6594d9a339be76506cb Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 29 Jun 2023 13:30:26 -0400 Subject: [PATCH] tag todos potentially useful for datalad --- doc/projects/datalad/potential.mdwn | 6 ++++++ doc/todo/Adressing_.gitattributes_inefficiency.mdwn | 1 + doc/todo/Incremental_git_annex_sync_--content_--all.mdwn | 1 + ...add_import_tree_to_external_special_remote_protocol.mdwn | 4 ++++ doc/todo/drop_from_export_remote.mdwn | 1 + doc/todo/external_remote_querying_transition.mdwn | 1 + doc/todo/git-annex-export_--from_option.mdwn | 1 + doc/todo/importtree_only_remotes.mdwn | 1 + ...clear_criteria_for_adding_git-annex-config_settings.mdwn | 1 + doc/todo/network_test_suite.mdwn | 1 + ...ssion_on_special_remotes_like___34__directory__34__.mdwn | 1 + doc/todo/stalldetection_for_import_and_export.mdwn | 1 + 12 files changed, 20 insertions(+) create mode 100644 doc/projects/datalad/potential.mdwn diff --git a/doc/projects/datalad/potential.mdwn b/doc/projects/datalad/potential.mdwn new file mode 100644 index 0000000000..1d3f59ca47 --- /dev/null +++ b/doc/projects/datalad/potential.mdwn @@ -0,0 +1,6 @@ +These are TODOs that have been tagged as potentially being useful for +[[/projects/DataLad]] or a related project to fund work on. + +[[!inline pages="todo/* and !todo/done and !link(todo/done) and +tagged(projects/datalad/potential))" sort=mtime feeds=no actions=yes archive=yes show=0 template=buglist]] + diff --git a/doc/todo/Adressing_.gitattributes_inefficiency.mdwn b/doc/todo/Adressing_.gitattributes_inefficiency.mdwn index 6debd4516e..a668a6d952 100644 --- a/doc/todo/Adressing_.gitattributes_inefficiency.mdwn +++ b/doc/todo/Adressing_.gitattributes_inefficiency.mdwn @@ -19,3 +19,4 @@ Couldn't the [separate-git-tree-for-diffing-technique you used lately to speed u One problem I see with this tough is that it wouldn't be possible to cache the user's `.git/info/attributes` settings, which can change independently. [[!tag confirmed]] +[[!tag projects/datalad/potential]] diff --git a/doc/todo/Incremental_git_annex_sync_--content_--all.mdwn b/doc/todo/Incremental_git_annex_sync_--content_--all.mdwn index 8eb0fb7f05..11ea484f52 100644 --- a/doc/todo/Incremental_git_annex_sync_--content_--all.mdwn +++ b/doc/todo/Incremental_git_annex_sync_--content_--all.mdwn @@ -18,3 +18,4 @@ So I have yet another idea to speed up git annex. For now only for the 2nd pass 2. Again, update the commit id of remotes that we successfully synced with. [[!tag confirmed]] +[[!tag projects/datalad/potential]] diff --git a/doc/todo/add_import_tree_to_external_special_remote_protocol.mdwn b/doc/todo/add_import_tree_to_external_special_remote_protocol.mdwn index a1eda94346..5c597df861 100644 --- a/doc/todo/add_import_tree_to_external_special_remote_protocol.mdwn +++ b/doc/todo/add_import_tree_to_external_special_remote_protocol.mdwn @@ -14,6 +14,9 @@ What I'd like to do is implement this in concert with someone who is implementing a special remote that uses it. So we can iterate on the protocol as needed to make it better. --[[Joey]] +> @mih expressed some interest in this in [a comment](https://git-annex.branchable.com/design/external_special_remote_protocol/export_and_import_appendix/#comment-d0cffbe55870a469052ebb7ed36f8300) +> so maybe him? --[[Joey]] + I do want to implement this though, assuming it turns out to be feasible for people to implement it despite its complexity, so I'm tagging this confirmed. @@ -22,3 +25,4 @@ although it might make sense to implement that as a simpler protocol extension.) [[!tag confirmed]] +[[!tag projects/datalad/potential]] diff --git a/doc/todo/drop_from_export_remote.mdwn b/doc/todo/drop_from_export_remote.mdwn index a010628a25..2783428ee9 100644 --- a/doc/todo/drop_from_export_remote.mdwn +++ b/doc/todo/drop_from_export_remote.mdwn @@ -29,3 +29,4 @@ from the remote. > file to be deleted from master. [[!tag confirmed]] +[[!tag projects/datalad/potential]] diff --git a/doc/todo/external_remote_querying_transition.mdwn b/doc/todo/external_remote_querying_transition.mdwn index f0399108a8..d18e23f157 100644 --- a/doc/todo/external_remote_querying_transition.mdwn +++ b/doc/todo/external_remote_querying_transition.mdwn @@ -50,3 +50,4 @@ Note that the protocol does allow querying with GETCONFIG etc before responding to a WHEREIS request. [[!tag confirmed]] +[[!tag projects/datalad/potential]] diff --git a/doc/todo/git-annex-export_--from_option.mdwn b/doc/todo/git-annex-export_--from_option.mdwn index a5f5df343a..372c3c8492 100644 --- a/doc/todo/git-annex-export_--from_option.mdwn +++ b/doc/todo/git-annex-export_--from_option.mdwn @@ -7,3 +7,4 @@ Which is caused by the fact that I didn't have checked out the files on my works Is there a reason that does not exist and if so what would be a way to do sending files to the android device without ssh-ing into my server? [[!tag confirmed]] +[[!tag projects/datalad/potential]] diff --git a/doc/todo/importtree_only_remotes.mdwn b/doc/todo/importtree_only_remotes.mdwn index 3df1cea549..f73a883b20 100644 --- a/doc/todo/importtree_only_remotes.mdwn +++ b/doc/todo/importtree_only_remotes.mdwn @@ -76,3 +76,4 @@ Or by complicating Remote.Helper.ExportImport further.. --[[Joey]] [[!tag confirmed]] +[[!tag projects/datalad/potential]] diff --git a/doc/todo/need_a_clear_criteria_for_adding_git-annex-config_settings.mdwn b/doc/todo/need_a_clear_criteria_for_adding_git-annex-config_settings.mdwn index dcf359dd51..fdb4e968b6 100644 --- a/doc/todo/need_a_clear_criteria_for_adding_git-annex-config_settings.mdwn +++ b/doc/todo/need_a_clear_criteria_for_adding_git-annex-config_settings.mdwn @@ -105,3 +105,4 @@ easy to fix up a git commit history to remove an unwanted commit. Does annex.resolvemerge meet criteria #1? --[[Joey]] [[!tag confirmed]] +[[!tag projects/datalad/potential]] diff --git a/doc/todo/network_test_suite.mdwn b/doc/todo/network_test_suite.mdwn index fafde3dcbb..5faffa75e7 100644 --- a/doc/todo/network_test_suite.mdwn +++ b/doc/todo/network_test_suite.mdwn @@ -31,3 +31,4 @@ running it on at least some of the autobuilders might be a good way. --[[Joey]] [[!tag confirmed]] +[[!tag projects/datalad/potential]] diff --git a/doc/todo/option_for___40__fast__41___compression_on_special_remotes_like___34__directory__34__.mdwn b/doc/todo/option_for___40__fast__41___compression_on_special_remotes_like___34__directory__34__.mdwn index c88d0ebb18..9410d3149b 100644 --- a/doc/todo/option_for___40__fast__41___compression_on_special_remotes_like___34__directory__34__.mdwn +++ b/doc/todo/option_for___40__fast__41___compression_on_special_remotes_like___34__directory__34__.mdwn @@ -6,3 +6,4 @@ For example, I use git annex for very large scientific tomographic datasets and Though, I guess, it would be possible to write a special remote wrapper for this, I wonder if this might qualify as an officially supported option to the already existing special remotes like "directory" or "rsync". E.g. in conjunction to `encryption` something like `compression` with possible values like `pbzip`, `bzip`, `pigz` and `gzip`. [[!tag confirmed]] +[[!tag projects/datalad/potential]] diff --git a/doc/todo/stalldetection_for_import_and_export.mdwn b/doc/todo/stalldetection_for_import_and_export.mdwn index c1e01f798a..6943918fb9 100644 --- a/doc/todo/stalldetection_for_import_and_export.mdwn +++ b/doc/todo/stalldetection_for_import_and_export.mdwn @@ -10,3 +10,4 @@ extended to cover the additional actions. --[[Joey]] > on. --[[Joey]] [[!tag confirmed]] +[[!tag projects/datalad/potential]] -- 2.30.2