Nguyen Thai Ngoc Duy wrote: > But empty trees are allowed in repo since 79b1138 (fsck.c: fix bogus > "empty tree" check). Index can't handle empty trees, so it's a bug to > me that index still accepts them as input and silently discard them. FWIW my instinct points in the opposite direction. I wouldn't mind seeing fsck warn about trees containing empty subtrees[1]. As for cache-tree, while it is not obvious what the right thing to do is, discarding empty subtrees sounds accepatable. For storage of empty subtrees in repos imported from svn, Yann's idea of using .gitattributes somehow (maybe in the parent directory or maybe in the subdir itself) seems oddly appealing. Just my unproductive two cents, Jonathan [1] I suspect 79b1138 was only meant to deal with the "git commit --allow-empty from newly initialized repo" case. -- 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