diff --git a/doc/todo/specify_freeze__47__thaw_scripts_relative_to_topdir/comment_4_c6523cd4ee7c50d13f641c40e022ab8d._comment b/doc/todo/specify_freeze__47__thaw_scripts_relative_to_topdir/comment_4_c6523cd4ee7c50d13f641c40e022ab8d._comment
deleted file mode 100644
index 494ac90786..0000000000
--- a/doc/todo/specify_freeze__47__thaw_scripts_relative_to_topdir/comment_4_c6523cd4ee7c50d13f641c40e022ab8d._comment
+++ /dev/null
@@ -1,15 +0,0 @@
-[[!comment format=mdwn
- username="yarikoptic"
- avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4"
- subject="may be %dotgit?"
- date="2025-01-06T23:38:54Z"
- content="""
-Original line of my thought was expressed in [this issue on github](https://github.com/dbic/handbook/issues/27).  
-One of the recent cases which made git-annex \"flip out\" into adjusted branch mode (yet to try to reproduce and follow up on [add_config_var_preventing_adjusted_branch_mode](https://git-annex.branchable.com/projects/datalad/bugs-done/add_config_var_preventing_adjusted_branch_mode/)), which happened when user executed datalad with git-annex inside a singularity container.
-To facilitate reproducibility etc, we are aiming to minimize effects of outside elements on execution within container so bind mount only current dataset and transfer only some [git / git-annex settings](https://github.com/ReproNim/containers/blob/master/scripts/singularity_cmd#L88).
-We could also check on paths for those scripts and bind mount them too. Also if relying on PATH, we would need somehow to ensure that inside the container PATH would point to them too (might be overridden by container's startup script since after all outside PATH might have little to do with inside -- think about running docker container on OSX).
-
-I think it would have been clean(er) if some initial invocation of current global git-annex freeze/thaw script which would potentially determine either it is needed or not at all (since some partitions might not need it, some need one kind, another - some other one), would instantiate in a given repository a copy of the specific freeze/thaw scripts tandem. But inability to specify relative path hinders that.  May be similarly to `%path` , it could have some `%dotgit` or alike variable to point to location of `.git` folder, and our \"freeze/thaw\" installation script populating values like `thawcontent-command = %dotgit/bin-annex/thaw-content %path`? I guess also could simply add treatment of leading `./` to signal being relative to `.git/` folder.  Such susbstitution would need to be done once upon reading that config setting per repo, there is no need to sense if script is there or not.  Since if not -- it better error out instead of proceeding forward with \"default\" behavior (which seems to be \"switch to adjusted branch\").
-
-
-"""]]