Re: remote.<name>.merge missing from the git-config man page?

From: Junio C Hamano <gitster@pobox.com>
Date: Mar 8, 2021, 17:27 UTC
Message-ID: <xmqqlfax7dya.fsf@gitster.c.googlers.com>
In-Reply-To: <CAOuwed4HJLTgk48Fre5vGYjYanqD6hu8yZM73CpcAmF1ajiTnA@mail.gmail.com>

Fabien Terrani <terranifabien@gmail.com> writes:

Show 5 quoted lines

> I was recently trying to understand the git-push command's behavior,
> especially regarding the configuration values's resolution. I read the
> following in the EXAMPLES section of the git-push man page:
>
>> git push origin

>>     Without additional configuration, pushes the current branch
>>     to the configured upstream (remote.origin.merge configuration
>>     variable) if it has the same name as the current branch, and
>>     errors out without pushing otherwise.

Hmph, it seems it talks about the branch on the remote side that is configured for the current branch to integrate with. Most likely that is misspelt "branch.<name>.merge" where <name> is the name of the branch currently checked out.

The text comes from b2ed944a (push: switch default from "matching" to "simple", 2013-01-04); I am a bit surprised how such a typo survived this long ;-)