git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Espen Antonsen" <espen@inspired.no>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: Git status parse error after v.2.22.0 upgrade
Date: Wed, 12 Jun 2019 14:47:11 +0200	[thread overview]
Message-ID: <38b0f33a-1da1-4231-802e-ae14d9843ad2@www.fastmail.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1906112127420.789@QRFXGBC-DHN364S.ybpnyqbznva>

I don't have any hooks, just the default sample scripts. GIT_TRACE doesn't show anything else.

On Tue, 11 Jun 2019, at 21:28, Johannes Schindelin wrote:
> Hi Espen,
> 
> On Tue, 11 Jun 2019, Espen Antonsen wrote:
> 
> > Seeing an error after upgrading to git v2.22.0.
> >
> > git status shows “error: could not parse ‘*a commit message from 2012*’”
> >
> > Downgrading to v.2.21.0 does not yield this message for git status.
> >
> > I can only replicate this in a private repo I have so far. Unable to
> > share the repo but can debug if you need more info.
> 
> Sounds like a hook gone haywire. Find out more by setting `GIT_TRACE=1`
> before repeating the command.
> 
> Ciao,
> Johannes
>

  reply	other threads:[~2019-06-12 12:47 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 [this message]
2019-06-12 18:47     ` Johannes Schindelin
2019-06-13  9:30       ` aleksandrs
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=38b0f33a-1da1-4231-802e-ae14d9843ad2@www.fastmail.com \
    --to=espen@inspired.no \
    --cc=Johannes.Schindelin@gmx.de \
    --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).