Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> writes: > On Thu, 19 Jul 2007, Junio C Hamano wrote: >> >> But you _could_ treat that "should-be-kept-even-when-empty"-ness >> just like we treat executable bit on blobs, I think. > > True. Or you could make it a path attribute and/or a per-repository > decision, so that while the data wouldn't necessarily be in the > database itself, the user could specify the behaviour he wanted. No, one can't. Once can decide per repository whether one wants to permit this kind of information in. But if one does, the information needs to there for _every_ tree. And a "." entry is a natural and intuitive way to do that. "." has been used as a directory entry for decades in Unix. >> This will involve a lot of changes, so I would not recommend >> anybody doing so, though. > > Agreed. The upside just isn't there. It is a good thing that you did not design the Unix file systems. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
