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

Re: [PATCH] docs: correct mistakes in git-merge

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 17, 2025, 17:28 UTC
Message-ID
<xmqq1pqe7mlw.fsf@gitster.g>
In-Reply-To
<6518dd3b-ca05-1ce8-e700-81167cd2e88e@gmx.de>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
Show 28 quoted lines
>> Additionally diagrams on the page are adjusted
>> to use spaces instead of tabs, so that they align
>> regardless of tab size. This is in line with
>> diagrams on other git documentation pages.
>
> To be precise, you could add to the commit message that the faulty
> description was introduced in 0c514d576685 (git-merge.txt: mention
> 'ORIG_HEAD' in the Description, 2023-01-10). (I Cc:ed Philippe Blain who
> authored that patch.)
> ...
>>  ------------
>> -	  A---B---C topic
>> -	 /
>> +          A---B---C topic
>> +         /
>
> ... while correcting the description seemed fairly straight-forward, this
> white-space change appears to tread on more delicate territory. It might
> deserve its own patch
> ...
>> @@ -38,11 +38,11 @@ Then `git merge topic` will replay the changes made on the
>>  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`).
>> +`ORIG_HEAD` is set to the tip of the current branch (`G`).
>
> This is obviously a good fix.

All comments are good ones for contributors to keep in mind for their next attempt.

For this particular one, which is already in 'master', there is no point in polishing and resending the patch, though ;-)

Thanks.
Previous: Johannes Schindelin
Message 3 of 3 in “docs: correct mistakes in git-merge”
  1. docs: correct mistakes in git-mergeTimur Sultanaev via GitGitGadget, Jul 5, 2025
  2. Johannes SchindelinJul 17, 2025
  3. Junio C HamanoJul 17, 2025

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.