Re: Git status parse error after v.2.22.0 upgrade

On Thu, Jun 13, 2019 at 09:05:16AM -0700, Junio C Hamano wrote: > are you getting it when you run "git status" command??? Yes, the regular old porcelain `git-status(1)`. $ git status error: could not parse '<>' On branch <> nothing to commit, working tree clean -- Best, Aleksandrs Ļedovskis

Re: Git status parse error after v.2.22.0 upgrade

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 J