On Thu, 19 Jul 2007, David Kastrup wrote: > > Well, kudos. Together with the analysis from Junio, this seems like a > good start. Would you have any recommendations about what stuff one > should really read in order to get up to scratch about git internals? Well, you do need to understand the index. That's where all the new subtlety happens. The data structures themselves are trivial, and we've supported empty trees (at the top level) from the beginning, so that part is not anything new. However, now having a new entry type in the index (S_IFDIR) means that anything that interacts with the index needs to think twice. But a lot of that is just testing what happens, and so the first thing to do is to have a test-suite. There's also the question about how to show an empty tree in a diff. We've never had that: the only time we had empty trees was when we compared a totally empty "root" tree against another tree, and then it was obvious. But what if the empty tree is a subdirectory of another tree - how do you express that in a diff? Do you care? Right now, since we always recurse into the tree (and then not find anything), empty trees will simply not show up _at_all_ in any diffs. And what about usability issues elsewhere? With my patch, doing something like a git add directory/ still won't do anything, because the behaviour of "git add" has always been to recurse into directories. So to add a new empty directory, you'd have to do git update-index --add directory and that's not exactly user-friendly. So do you add a "-n" flag to "git add" to tell it to not recurse? Or do you always recurse, but then if you notice that the end result is empty, you add it as a directory? All the logic for that whole directory lookup is in git/dir.c, and that code takes various flags because different programs want different things (show "ignored" files, or ignore them? Show empty directories or ignore them? etc). So primarily, I think the job is: - thinking about the index, and the interactions when adding a directory or adding files under a directory that already exists. I *think* we get all the corner cases right, because they should be exactly the same as with subprojects, but hey, maybe there's some piece that tests S_ISGITLINK() and now needs a S_ISDIR() test too.. - adding test cases - thinking about the user interfaces for this, and adding code to handle directories where needed (eg the above "git add" issue). - thinking about merges (which is largely about the index too, but is a whole 'nother set of issues, with multiple stages in the same index at the same time) It might all be trivial. The directory traversal already knows that empty directories are special, so getting the right behaviour to "git add" may be really really easy. Or maybe it's not. I think a lot of it is just finding what needs to be done, seeign if we already do it, and if not, seeign how to do it. Boring test-cases, in other words. Linus - 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
