4 ms·
Maybe the correct thing to do is to modify git so that it can track an otherwise-empty directory and then never have to worry about this problem again. Is there
by JuniperMesos 8mo ago
Maybe the correct thing to do is to modify git so that it can track an otherwise-empty directory and then never have to worry about this problem again. Is there a reason why this is hard to integrate into git's existing model of the filesystem?
- lucketone 8mo ago1. Nobody sees this as a big issue. 2. As-is situation is good enough. 3. I guarantee that you will have colleagues that will accidentally add empty dirs. (I definitely have seen when they accidentally add built artefacts; dirs would be lesser issue as they would not increase repo size by much, but still) 4. Actually only first two reasons matter, but for nitpickers there would be also a bit dishonest but formally correct pointing to some doc saying that it is file or content tracker (and formally directory is not a content)
- 1718627440 8mo agoGit only tracks files not directories, so yeah you would need to change a lot. It is also unclear what the semantics should be. What is with a directory that is tracked as r--, but then files get added?