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

Re: fatal: unable to read after commit

From
Christian Couder <christian.couder@gmail.com>
Date
Apr 12, 2019, 08:39 UTC
Message-ID
<CAP8UFD0bBBtOOz9ew_2URCp3nY1v0_OHMby1-N+T0nCDW82DRg@mail.gmail.com>
In-Reply-To
<20190411164440.GC12669@ikki.ethgen.ch>
Hi,
On Thu, Apr 11, 2019 at 7:24 PM Klaus Ethgen <Klaus@ethgen.ch> wrote:
Show 5 quoted lines
> I am a heavy user of git now at version 2.20.1 on debian.
>
> Since some weeks I have the problem that I get often "fatal: unable to
> read ..." and a unclear repository after a git commit. The commit itself
> is correct and so a git reset --hard helps to fix the issue.
Could you tell us at least which Debian version and file system you use?

Would you be ok to bisect it or at least tell us if it happens with 2.19.2, 2.20.0 and 2.21.0?

> Any Idea what could be the reason for that problem. I encounter it on
> different repositories so not limited to one.

Is it easy to reproduce even on very small test repos? Could you send us a small script that reproduces it?

Could you also run the Git test suite on your machine?

Thanks, Christian.

Previous: Klaus EthgenNext: Klaus Ethgen
Message 2 of 7 in “fatal: unable to read after commit”
  1. Klaus EthgenApr 11, 2019
  2. Christian CouderApr 12, 2019
  3. Klaus EthgenApr 12, 2019
  4. Klaus EthgenApr 12, 2019
  5. Klaus EthgenApr 12, 2019
  6. Klaus EthgenApr 13, 2019
  7. Jeff KingApr 22, 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.