Heya, On Thu, Oct 7, 2010 at 12:55, David Barr <david.barr@xxxxxxxxxxxx> wrote: > Most git commands do their writing to the object db via the index and > loose objects. ÂWhen you just have a pile of trees you want to convert > into commits, this is wasteful; for performance-critical operations > like filter-branch --subdirectory-filter, one might want a sort of > hash-object --batch-to-pack to write a pack directly. This means nothing to me, but perhaps I'm not the target audience of this paragraph. > Fortunately we have fast-import (which is one of the only git commands > that will write to a pack directly) but there is not an advertised way > to tell fast-import to use a given tree for its commits. I'm with you up to "use a given tree for its commits". > This patch changes that, by allowing > > Â Â Â ÂM 040000 <tree id> "" > > as a filemodify line in a commit to reset to a particular tree without > any need to unpack it. ÂFor example, > > Â Â Â ÂM 040000 4b825dc642cb6eb9a060e54bf8d69288fbee4904 "" > > is a synonym for the deleteall command. Ok, so maybe I do understand, is it basically 'git read-tree 4b825dc642cb6eb9a060e54bf8d69288fbee4904' for fast-import? -- Cheers, Sverre Rabbelier -- 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