Seth Falcon <sethfalcon@xxxxxxxxx> wrote: > Pazu <pazu@xxxxxxxxxxx> writes: > > Notice that there's no "CamelEar" directory. For some reason, it > > wasn't fetched in the initial revision. Now, just to make sure this > > isn't svn fault: > > > > mini:~/devel/camel-git pazu$ svn ls -r11143 > > https://tech.bga.bunge.com/BungeHomeExt/GLS/trunk/java/bg-cam > > .cvsignore > > BungeIntegrationEar/ > > BungeIntegrationService/ > > BungeIntegrationServiceClient/ > > CamelEar/ > > Is CamelEar an empty directory (or was it an empty directory in the > first fetch) by any chance? > > I think that presently git-svn does not create empty dirs when pulling > from svn. It would be nice to have such directories created since > some projects will expect the empty dir to be there (no need to track > it in git, IMO). Git itself cannot easily track empty directories (at least as far as update-index and checkout) goes. What I *can* do is run mktree and to force the creation of tree objects with a 4b825dc642cb6eb9a060e54bf8d69288fbee4904 (empty) sub tree and run commit-tree on it, but checkout/checkout-index would still need to be modified to support it. Is that something the git community wants? -- Eric Wong - 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