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
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jun 12, 2019, 18:47 UTC
Message-ID
<nycvar.QRO.7.76.6.1906122046400.789@QRFXGBC-DHN364S.ybpnyqbznva>
In-Reply-To
<38b0f33a-1da1-4231-802e-ae14d9843ad2@www.fastmail.com>
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

Previous: Espen AntonsenNext: aleksandrs@ledovskis.lv
Message 4 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.