On Thu, 19 Jul 2007, Junio C Hamano wrote: > > Brian Gernhardt <benji@xxxxxxxxxxxxxxxxxx> writes: > > > My apologies for the wasted bandwidth arguing for things that had > > already been decided. > > Sorry, who decided what? I think people who didn't know how the world works decided that directories that were added manually as directories would stay as directories even after the last file was removed. That's physically impossible with the git data-structures (since there is no way of saving "this directory was added empty" in the tree structures, nor any point to it), so I think it's just insane rambling. I dunno. I think empty directories are worth supporting, mainly to be able to capture other SCM's notion of what _they_ track, but quite frankly, the level of discussion about them hasn't been exactly inspiring. It seems to be more about "this is what we'd like to see, without really having a reason for it, nor necessarily understanding what we're talking about" than "this is realistic and useful and here are patches". I *do* think that it's a very valid argument that if you import something from SVN that has an empty directory, the git import should show that. That's about the only valid argument I've ever seen for them, though, and I think that's totally irrelevant to such issues as to whether "git rm file/in/directory" should remove the directory(*) from being tracked by git when the file goes away or not. Linus (*) And, for anybody confused about the issue, the answer to the latter question is an emphatic: "Yes it should, live with it, and if you want the directory back, you had better add it back as an empty directory" - 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
