Git development
 help / color / mirror / Atom feed
From: "Ramkumar Ramachandra" <r@artagnon.com>
To: "Git List" <git@vger.kernel.org>
Subject: User report on git 2.55.0
Date: Fri, 04 Sep 2026 19:05:43 +0100	[thread overview]
Message-ID: <7fb200e9-ff28-4b22-9d9e-dbdec83c2835@app.fastmail.com> (raw)

Hi,

I recently bumped to the latest version of git on macOS via homebrew, and here's what I've noticed:

1. git-replay now updates the ref, simplifying my git-reply-checkout script. Someone on this list recommended it to me in response to an issue I had a long time ago, and I think I can safely say that git-replay is an invaluable tool. Thanks!
2. git-pull often fails with a dangling remote ref error, and fails to update the current branch (main, in my case): the workaround is to reset-hard to origin/main. I'm not sure if this is a GitHub issue, or a bug in core git: I've never encountered this behavior on older versions of git, with the exception of submodules.
3. git-diff sometimes exits with 0 code without printing a diff, even though the worktree is dirty: the workaround is to run it again. I've never encountered this behavior on older versions of git, and I think it might be a subtle race in core git.
4. `git checkout -` sometimes fails with an invalid ref error after a pull, where the previous branch is a local branch. I don't know if this is due to a background git-gc with some behavior change, but I never encountered this behavior on older versions without an operation that would cause this.

Before digging further to find the root cause, I'd like to know if there is some explanation I'm missing, or if these are known issues?

Thanks.

Warm regards,
Ram

             reply	other threads:[~2026-09-04 18:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04 18:05 Ramkumar Ramachandra [this message]
2026-09-04 19:22 ` User report on git 2.55.0 brian m. carlson
2026-09-04 20:32   ` Ramkumar Ramachandra
2026-09-04 23:10     ` Ramkumar Ramachandra
2026-09-04 23:20       ` Ben Knoble
2026-09-04 23:42         ` Ramkumar Ramachandra

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7fb200e9-ff28-4b22-9d9e-dbdec83c2835@app.fastmail.com \
    --to=r@artagnon.com \
    --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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox