Hi, > | For a command (like filter-branch --subdirectory-filter) that wants > | to commit a lot of trees that already exist in the object db, writing > | undeltified objects as loose files only to repack them later can > | involve a significant amount[*] of overhead. > [*] how significant? Numbers are always nice. :) Using git hash-object: real 2m51.748s user 0m25.460s sys 0m23.890s Using git fast-import: real 2m13.337s user 0m28.010s sys 0m18.100s > > > Ok, so maybe I do understand, is it basically 'git read-tree > > 4b825dc642cb6eb9a060e54bf8d69288fbee4904' for fast-import? > Perhaps mention that in the commit message as well then. Of course, > the fast-import doc needs updating, and it needs test. | is a synonym for the deleteall command and the fast-import equivalent of | | git read-tree 4b825dc642cb6eb9a060e54bf8d69288fbee4904 -- David Barr -- 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