On Thu, Aug 20, 2020 at 01:34:45PM +0200, Lukas Straub wrote: > Yes, there are many workarounds and they work well in the CI usecase. However, > for the arbitrary files usecase there is no good workaround. I currently use > a script which iterates over the tree and renames .git -> dotgit before running > any git command and back again afterwards, but it is slow and brittle. I toyed > with the idea of writing a FUSE filesystem to do the renaming, but it is > needlessly complex and hurts performance. > > Really, this problem should be solved in git itself. It is unclear to me why need to hold many sub-repositories within the parent one, nor what Git operations you expect to perform over them. And what disadvantages your script solution has. Perhaps you can give a more concrete use-case (but before you spend a lot of time doing so, I'll warn you that I find it pretty unlikely that it will cross the bar necessary to counter the downsides we've discussed so far). -Peff
