diff --git a/doc/todo/Describe_a_file_in_function_of_another_file.mdwn b/doc/todo/Describe_a_file_in_function_of_another_file.mdwn
new file mode 100644
index 0000000000..4df53b795a
--- /dev/null
+++ b/doc/todo/Describe_a_file_in_function_of_another_file.mdwn
@@ -0,0 +1,16 @@
+Hello,
+
+In order to save space/bandwith/... I would like to create a way to describe a file compared to another. You could see this as a kind of very special "remote" (which is local :P), that says "To produce file XXX, take file YYY, and run command CCC with args YYY".
+
+You may ask why it is useful? I have several usecases:
+
+1) my first usecase is that I would like to be able to generate thumbnails for my pictures in order to speed up display. A thumbnail can be easily created from a picture (with for example the convert command), but when you don't need the thumbnail, you may prefer to remove them locally to save space.
+
+2) similarly, I have some RAW photo files, and a script to turn them into .JPG file. Or even better, I could have several scripts to convert my initial RAW files into several .JPG files, with different parameters/look. Keeping both RAW and developed JPG can be heavy, so this kind of tool could allow me to remove the .JPG file(s) when I don't need them anymore, so I don't mind to drop the .JPG file as soon as the RAW does exist (but if the RAW does not exist anymore, I shouldn't be able to remove the .JPG of course).
+
+3) I also have on my desktop some compressed files (.iso for example, or old projects). Most of the time, I don't really need to keep the uncompressed .iso, but from time to time, I may need them. For now I manually uncompress them, use them, and delete them... But it could be cool to let git-annex deal with them automatically.
+
+Does git-annex provide such functionnality? If not, do you think it could be implementable?
+
+Thanks!
+ 
diff --git a/doc/todo/Describe_a_file_in_function_of_another_file/comment_1_b0132288c67054485e9681f3f5138768._comment b/doc/todo/Describe_a_file_in_function_of_another_file/comment_1_b0132288c67054485e9681f3f5138768._comment
new file mode 100644
index 0000000000..6ea202b65e
--- /dev/null
+++ b/doc/todo/Describe_a_file_in_function_of_another_file/comment_1_b0132288c67054485e9681f3f5138768._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="Ilya_Shlyakhter"
+ avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0"
+ subject="comment 1"
+ date="2019-10-03T00:36:54Z"
+ content="""
+See [related discussion](https://github.com/datalad/datalad/issues/2850)
+"""]]
diff --git a/doc/todo/Describe_a_file_in_function_of_another_file/comment_2_4efe2044282c8ccd6d570e84bb2ab68a._comment b/doc/todo/Describe_a_file_in_function_of_another_file/comment_2_4efe2044282c8ccd6d570e84bb2ab68a._comment
new file mode 100644
index 0000000000..cf19d83bd0
--- /dev/null
+++ b/doc/todo/Describe_a_file_in_function_of_another_file/comment_2_4efe2044282c8ccd6d570e84bb2ab68a._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="tobiasBora"
+ avatar="http://cdn.libravatar.org/avatar/80a7d8c2a7b475b6b71198cce0faa6b0"
+ subject="comment 2"
+ date="2019-10-03T00:48:23Z"
+ content="""
+So if I get it, it's interesting, but not implemented, and mayae tricky to implement? (The discution is dead now)
+"""]]
diff --git a/doc/todo/support_multiple_special_remotes_with_same_uuid/comment_7_cad7edecb526f3bdf9bcff5aa3569f91._comment b/doc/todo/support_multiple_special_remotes_with_same_uuid/comment_7_cad7edecb526f3bdf9bcff5aa3569f91._comment
new file mode 100644
index 0000000000..eb221f22fb
--- /dev/null
+++ b/doc/todo/support_multiple_special_remotes_with_same_uuid/comment_7_cad7edecb526f3bdf9bcff5aa3569f91._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="Ilya_Shlyakhter"
+ avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0"
+ subject="different repos with same uuid"
+ date="2019-10-02T15:13:55Z"
+ content="""
+\"It is already possible of course for two git remotes to have the same uuid, and also for a special remote and git remotes to have the same uuid\" -- but, in general, that's a situation to be avoided, right?  Other than two protocols accessing the same datastore, are there times when you'd want that?
+
+(Related: [[`git-annex-reinit`|git-annex-reinit]], [[todo/reinit_current_repo_to_new_uuid]])
+"""]]