From: Duy Nguyen <pclouds@gmail.com>
To: "McHenry, Matt" <mmchenry@carnegielearning.com>
Cc: Junio C Hamano <gitster@pobox.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: recovering from "unordered stage entries in index" error
Date: Sun, 24 May 2015 16:52:37 +0700 [thread overview]
Message-ID: <CACsJy8B=ttGa1aBKTdZAe6bLN4rbEE1r3fA+ifNNvUWhYD0Yfg@mail.gmail.com> (raw)
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
next prev parent reply other threads:[~2015-05-24 9:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 13:48 recovering from "unordered stage entries in index" error McHenry, Matt
2015-05-19 15:19 ` Junio C Hamano
2015-05-19 16:51 ` McHenry, Matt
2015-05-21 9:56 ` Duy Nguyen
2015-05-21 13:19 ` McHenry, Matt
2015-05-21 16:49 ` Junio C Hamano
2015-05-22 0:17 ` Duy Nguyen
2015-05-22 18:56 ` McHenry, Matt
2015-05-23 2:06 ` Duy Nguyen
2015-05-23 2:47 ` McHenry, Matt
2015-05-24 9:52 ` Duy Nguyen [this message]
2015-05-26 13:28 ` McHenry, Matt
2015-05-26 13:37 ` Duy Nguyen
[not found] ` <805ACAFCB18CC2408F45D98ABEC64B650A06EC538B@exchdb01>
2015-05-23 21:36 ` McHenry, Matt
2015-05-22 19:24 ` Junio C Hamano
2015-05-22 19:57 ` McHenry, Matt
2015-05-23 17:06 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACsJy8B=ttGa1aBKTdZAe6bLN4rbEE1r3fA+ifNNvUWhYD0Yfg@mail.gmail.com' \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mmchenry@carnegielearning.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).