todo/what if there is a Git repo somewhere underneath /etc?etckeeperhttp://etckeeper.branchable.com/todo/what_if_there_is_a_Git_repo_somewhere_underneath___47__etc__63__/etckeeperikiwiki2022-11-08T17:25:58Zcomment 1http://etckeeper.branchable.com/todo/what_if_there_is_a_Git_repo_somewhere_underneath___47__etc__63__/comment_1_3d18e005c10b5f3e671fe6c12e5aa03d/alan.christopher.jenkins2021-10-17T13:52:29Z2017-01-05T12:41:13Z
What happened to me was that .etckeeper bloats up with files from the .git directories. Also it behaved confusingly different depending on the exact sequence of events. My notes on this are <a href="https://unix.stackexchange.com/questions/323489/i-have-nested-git-repos-will-it-cause-a-problem">here</a>
comment 2http://etckeeper.branchable.com/todo/what_if_there_is_a_Git_repo_somewhere_underneath___47__etc__63__/comment_2_48e36e7c4b88b27129650e9c447a374c/joey2021-10-17T13:52:29Z2020-05-05T20:38:57Z
<p>Gave this a try, and the nested repo gets commited as a submodule, which
makes a certain amount of sense. But /etc/.etckeeper includes directories
and files inside the rested repo, including even in its .git/ directory.</p>
<p>The way pre-commit.d/30store-metadata finds files, and empty
subdirectories, would need to be changed to take nested git repos into
account. I don't immediately see a good way.</p>
comment 3http://etckeeper.branchable.com/todo/what_if_there_is_a_Git_repo_somewhere_underneath___47__etc__63__/comment_3_f3618a15792640feef3f055ac108e940/anarcat2022-11-08T17:25:58Z2022-11-08T17:25:58Z
i think the proper solution here is to stop trying to replace gitignore with our own implementation and defer everything to <code>git-ls-files</code>. i lay out that idea in <a href="http://etckeeper.branchable.com/todo/metadata_ignore_filters_do_not_work/">metadata ignore filters do not work</a> and would very much welcome feedback on that.