Hi, On Wed, 18 Jul 2007, David Kastrup wrote: > The FAQ answer is weazeling on several accounts: > > a) No, git only cares about files, or rather git tracks content and > empty directories have no content. > > In the same manner as empty regular files have no contents, and git > tracks those. Existence and permissions are important. We do not track permissions of directories at all. This is because Git is primarily meant to track source code, and most "permissions" (i.e. restrictions) do not make any sense there. > b) The problem is not just that empty directories don't get added into > the repository. They also don't get removed again when switching to a > different checkout. When git-diff returns zero, I expect a subsequent > checkout to not leave complete empty hierarchies around because git > can't delete any empty leaves which it chose not to track. I _like_ the behaviour that Git does not remove a directory it added, when I put some untracked file into it. And switching back to that branch, Git has no problems, because it sees that the directory is already there. In case of a file, it would complain, and rightfully so. See the fundamental difference between a file and a directory now? I think it boils down to "an empty directory has _no_ contents, but an empty file has an _empty_ content". Ciao, Dscho - 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
