From: aleksandrs@ledovskis.lv
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Espen Antonsen <espen@inspired.no>, git@vger.kernel.org
Subject: Re: Git status parse error after v.2.22.0 upgrade
Date: Thu, 13 Jun 2019 12:30:23 +0300 [thread overview]
Message-ID: <20190613093023.GA3919@ariake.ledovskis.lv> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1906122046400.789@QRFXGBC-DHN364S.ybpnyqbznva>
Hello,
Managed to repro this problem on my private repo too.
Bisect points to b51a0fdc3822c2ef260f6d496b6df6d33b101e8a
However, I think the real culprit is 4a72486de97b5c6b0979b2b51e50c268bdb0d4f6, specifically `parse_insn_line` call.
My repo indeed contains a ".git/sequencer/todo" file which contains references to commits long-gone (i.e., rebased).
Renaming or deleting this file stops whines about "error: could not parse".
--
Regards,
Aleksandrs Ļedovskis
On Wed, Jun 12, 2019 at 08:47:27PM +0200, Johannes Schindelin wrote:
> Hi Espen,
>
> On Wed, 12 Jun 2019, Espen Antonsen wrote:
>
> > I don't have any hooks, just the default sample scripts. GIT_TRACE
> > doesn't show anything else.
>
> Okay, it was just a guess.
>
> And here is another guess: unless you impart with more details about your
> test case, I guess there is little anybody else can do to help you.
>
> Ciao,
> Johannes
next prev parent reply other threads:[~2019-06-13 15:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 12:58 Git status parse error after v.2.22.0 upgrade Espen Antonsen
2019-06-11 19:28 ` Johannes Schindelin
2019-06-12 12:47 ` Espen Antonsen
2019-06-12 18:47 ` Johannes Schindelin
2019-06-13 9:30 ` aleksandrs [this message]
2019-06-13 16:05 ` Junio C Hamano
2019-06-13 16:24 ` Jeff King
2019-06-13 17:43 ` Phillip Wood
2019-06-13 19:00 ` Jeff King
2019-06-25 13:25 ` Phillip Wood
2019-06-13 16:58 ` SZEDER Gábor
2019-06-13 17:11 ` Aleksandrs Ļedovskis
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=20190613093023.GA3919@ariake.ledovskis.lv \
--to=aleksandrs@ledovskis.lv \
--cc=Johannes.Schindelin@gmx.de \
--cc=espen@inspired.no \
--cc=git@vger.kernel.org \
/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).