Git development
 help / color / mirror / Atom feed
From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
To: mg@evolution515.net, git@vger.kernel.org
Subject: Re: git rebase writes worktree "Ref ... checked out at ..." todo comments with a hardcoded '#', breaking parsing when core.commentChar is not '#'.
Date: Mon, 03 Aug 2026 10:21:30 +0200	[thread overview]
Message-ID: <d0de4f3f-0f57-4458-a721-d5d8eb048ead@app.fastmail.com> (raw)
In-Reply-To: <20260803080254.38A0459466E8@dd18010.kasserver.com>

On Mon, Aug 3, 2026, at 10:02, Markus Geiger wrote:
> Ok, you can close it. I couldn't reproduce it in newer versions.
>
> Sorry, for taking up your time.
>
>
> The bug reproduces on your 2.43.0 but is gone in the newest git
> (2.55.0). It also doesn't reproduce on 2.39.5, which means this was a
> regression introduced somewhere in the 2.40–2.43 range and later fixed
> upstream — not a longstanding bug.
>
>
> ┌─────────────────┬─────────────────┬────────────────┐
> │   git version   │     Source      │     Result     │
> ├─────────────────┼─────────────────┼────────────────┤
> │ 2.39.5          │ debian bookworm │ ✅ not present │
> ├─────────────────┼─────────────────┼────────────────┤
> │ 2.43.0          │ your host       │ ❌ BUG PRESENT │
> ├─────────────────┼─────────────────┼────────────────┤
> │ 2.55.0 (newest) │ alpine edge     │ ✅ FIXED       │
> └─────────────────┴─────────────────┴────────────────┘
>[snip]

This was fixed in 94304b9f (sequencer: comment checked-out branch
properly, 2024-11-25) which was released in Git 2.48.0.

  reply	other threads:[~2026-08-03  8:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260803094639.0B7DB5946343@dd18010.kasserver.com>
2026-08-03  8:02 ` git rebase writes worktree "Ref ... checked out at ..." todo comments with a hardcoded '#', breaking parsing when core.commentChar is not '#' Markus Geiger
2026-08-03  8:21   ` Kristoffer Haugsbakk [this message]
2026-08-03  7:46 Markus Geiger

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=d0de4f3f-0f57-4458-a721-d5d8eb048ead@app.fastmail.com \
    --to=kristofferhaugsbakk@fastmail.com \
    --cc=git@vger.kernel.org \
    --cc=mg@evolution515.net \
    /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