git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Christian Couder <christian.couder@gmail.com>
To: Klaus Ethgen <Klaus@ethgen.ch>
Cc: git <git@vger.kernel.org>
Subject: Re: fatal: unable to read after commit
Date: Fri, 12 Apr 2019 10:39:02 +0200	[thread overview]
Message-ID: <CAP8UFD0bBBtOOz9ew_2URCp3nY1v0_OHMby1-N+T0nCDW82DRg@mail.gmail.com> (raw)
In-Reply-To: <20190411164440.GC12669@ikki.ethgen.ch>

Hi,

On Thu, Apr 11, 2019 at 7:24 PM Klaus Ethgen <Klaus@ethgen.ch> wrote:

> 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.

  reply	other threads:[~2019-04-12  8:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-11 16:44 fatal: unable to read after commit Klaus Ethgen
2019-04-12  8:39 ` Christian Couder [this message]
2019-04-12  9:14   ` Klaus Ethgen
2019-04-12  9:28   ` Klaus Ethgen
2019-04-12  9:30   ` Klaus Ethgen
2019-04-13  9:21   ` fatal: unable to read after commit - deeper analysis Klaus Ethgen
2019-04-22 16:21     ` Jeff King

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=CAP8UFD0bBBtOOz9ew_2URCp3nY1v0_OHMby1-N+T0nCDW82DRg@mail.gmail.com \
    --to=christian.couder@gmail.com \
    --cc=Klaus@ethgen.ch \
    --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).