From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
To: "Fabian Kratz" <fabian.kratz@proton.me>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Typo in man page for git-merge
Date: Sat, 05 Sep 2026 19:00:47 +0200 [thread overview]
Message-ID: <abd6ddbb-7981-4b1b-b050-73ced5b2960b@app.fastmail.com> (raw)
In-Reply-To: <T7GtKqbLStRVv4G9RYr5tCWEEkfQ5s-KzbS0OeeKfVArboamsIObGafTbl_XHsXRcCP3XjsR0xEqOsU3OzGVIurZWLGOnsUO9ZUn9UG0XHo=@proton.me>
Hi Fabian
On Sat, Sep 5, 2026, at 18:29, Fabian Kratz wrote:
> Hi, I just read the git man page git-merge and believe that I found a
> typo/error in an example. I don't know if this is the right place to
> post this, but this is the section:
>
>> Assume the following history exists and the current branch is "master":
>>
>> A---B---C topic
>> /
>> D---E---F---G master
>>
>> Then "git merge topic" will replay the changes made on the topic branch since it diverged from master (i.e.,
>> E) until its current commit (C) on top of master, and record the result in a new commit along with the names
>> of the two parent commits and a log message from the user describing the changes. Before the operation,
>> ORIG_HEAD is set to the tip of the current branch (C).
>
> I believe ORIG_HEAD is actually set to G here, not C. My own
> experiments support this and it's what I would expect after reading the
> explanation.
This was fixed in Git 2.51.0. Specifically in 953049ee (docs: correct
ORIG_HEAD example in "git merge" documentation, 2025-07-05).
prev parent reply other threads:[~2026-09-05 17:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-05 16:29 Typo in man page for git-merge Fabian Kratz
2026-09-05 17:00 ` Kristoffer Haugsbakk [this message]
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=abd6ddbb-7981-4b1b-b050-73ced5b2960b@app.fastmail.com \
--to=kristofferhaugsbakk@fastmail.com \
--cc=fabian.kratz@proton.me \
--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