Fatal error running status in new repo · Jacob Helwig <hidden> · 2016-06-15
Re: Fatal error running status in new repo · Jeff King <hidden> · 2016-06-15
Re: Fatal error running status in new repo · Jacob Helwig <hidden> · 2016-06-15
Re: Fatal error running status in new repo · Jeff King <hidden> · 2016-06-15
[PATCH] dwim_ref: fix dangling symref warning · Jeff King <hidden> · 2016-06-15
Re: Fatal error running status in new repo · Jeff King <hidden> · 2016-06-15
[PATCH] submodule summary: Don't barf when invoked in an empty repo · Johan Herland <hidden> · 2016-06-15
Re: [PATCH] submodule summary: Don't barf when invoked in an empty repo · Jeff King <hidden> · 2016-06-15

Re: Fatal error running status in new repo

From: Jeff King <hidden>
Date: 2016-06-15 22:48:17

On Mon, Feb 15, 2010 at 10:24:22PM -0800, Jacob Helwig wrote:

$ GIT_TRACE=1 git status
trace: built-in: git 'status'
# On branch master
#
# Initial commit
#
trace: run_command: 'submodule' 'summary' '--cached' '--for-status' '--summary-limit' '-1' 'HEAD'

Ah, OK. That is why I did not see it; I don't have submodulesummary
turned on.

I can reproduce your problem. The messages are actually from two
different spots. The first is actually a bug in the code I mentioned
earlier, and I'm still tracking down the second. Patches in a moment.

-Peff

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help