From 996f14c02b2647d5846debd8dd8537bbbe47ab89 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Jakub=20Je=C4=8Dm=C3=ADnek?= Date: Sun, 29 Jun 2025 21:04:45 +0200 Subject: [PATCH] doc: improve formatting in branch section MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit The 'branch' section of the git-config documentation was missing inline code formatting and emphasis for the placeholder. Both changes improve readability, especially when viewed online. Signed-off-by: Jakub Ječmínek Signed-off-by: Junio C Hamano --- Documentation/config/branch.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/config/branch.adoc b/Documentation/config/branch.adoc index e35ea7ac64..a4db9fa5c8 100644 --- a/Documentation/config/branch.adoc +++ b/Documentation/config/branch.adoc @@ -69,9 +69,9 @@ This option defaults to `never`. `git fetch`) to lookup the default branch for merging. Without this option, `git pull` defaults to merge the first refspec fetched. Specify multiple values to get an octopus merge. - If you wish to setup `git pull` so that it merges into from + If you wish to setup `git pull` so that it merges into __ from another branch in the local repository, you can point - branch..merge to the desired branch, and use the relative path + `branch..merge` to the desired branch, and use the relative path setting `.` (a period) for `branch..remote`. `branch..mergeOptions`:: -- 2.47.2