git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Git status parse error after v.2.22.0 upgrade

From
AĻAleksandrs Ļedovskis <aleksandrs@ledovskis.lv>
Date
Jun 13, 2019, 17:11 UTC
Message-ID
<20190613171106.GC3919@ariake.ledovskis.lv>
In-Reply-To
<xmqqr27xwjwj.fsf@gitster-ct.c.googlers.com>
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 '<<full contents of .git/sequencer/todo here>>' On branch <<some-branch>> nothing to commit, working tree clean

-- Best, Aleksandrs Ļedovskis

Previous: SZEDER Gábor
Message 12 of 12 in “Git status parse error after v.2.22.0 upgrade”
  1. Espen AntonsenJun 11, 2019
  2. Johannes SchindelinJun 11, 2019
  3. Espen AntonsenJun 12, 2019
  4. Johannes SchindelinJun 12, 2019
  5. aleksandrs@ledovskis.lvJun 13, 2019
  6. Junio C HamanoJun 13, 2019
  7. Jeff KingJun 13, 2019
  8. Phillip WoodJun 13, 2019
  9. Jeff KingJun 13, 2019
  10. Phillip WoodJun 25, 2019
  11. SZEDER GáborJun 13, 2019
  12. Aleksandrs ĻedovskisJun 13, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.