On Sat, May 23, 2015 at 1:56 AM, McHenry, Matt <mmchenry@xxxxxxxxxxxxxxxxxxxx> wrote: > $ git svn fetch > fatal: unordered stage entries in index > write-tree: command returned error: 128 git-svn does not create the index manually. It uses update-index or read-tree to do that. While there's still a chance of bugs in update-index that produces broken index, it's probably read-tree in this case because it assumes good order from the source tree object, which is(?) generated by git-svn. And the write-tree message supports this (the code does read-tree then write-tree). So maybe you can do "GIT_TRACE=2 git svn fetch" and post the output. I'd expect to see something like "git read-tree <sha1>" before "fatal: unorder...". You can then use git ls-tree <sha1> to examine this tree, try to sort the file list with "LANG=C sort" and compare with the original list. -- Duy -- 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