From: Duy Nguyen <pclouds@gmail.com>
Date: Sun, 24 May 2015 09:52:37 GMT
Subject: Re: recovering from "unordered stage entries in index" error
Message-ID: <CACsJy8B=ttGa1aBKTdZAe6bLN4rbEE1r3fA+ifNNvUWhYD0Yfg@mail.gmail.com>
In-Reply-To: <D377A9280DB18546A2471214D5CBB0E9087568F592@exchdb01>

On Sat, May 23, 2015 at 9:47 AM, McHenry, Matt
<mmchenry@carnegielearning.com> wrote:
>> 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.
>
>         There is no read-tree in the output (below).  The sha1 that is mentioned, 74332b7, is the one for the current trunk:

Hm.. neither read-tree nor update-index is in the output. I can see
git-svn closing stderr sometimes, but not sure if that's why we don't
see these commands, or something else. Could you try again with
GIT_TRACE=/absolute/path/to/some/where instead of GIT_TRACE=2 and post
the content of /abso../some/where?
-- 
Duy