All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Brandon Dong via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Brandon Dong <brandondong96@gmail.com>,
	Brandon <brandondong96@gmail.com>
Subject: [PATCH] doc: add missing --message long option to merge docs
Date: Fri, 29 May 2026 01:55:26 +0000	[thread overview]
Message-ID: <pull.2315.git.git.1780019726297.gitgitgadget@gmail.com> (raw)

From: Brandon <brandondong96@gmail.com>

Include mention of --message flag in merge docs to match what is
accepted (builtin/merge.c) and to make it consistent with the git
commit docs.

Signed-off-by: Brandon Dong <brandondong96@gmail.com>
---
    doc: add missing --message long option to merge docs

Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2315%2Fbrandondong%2Fmerge_message_docs-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2315/brandondong/merge_message_docs-v1
Pull-Request: https://github.com/git/git/pull/2315

 Documentation/git-merge.adoc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/Documentation/git-merge.adoc b/Documentation/git-merge.adoc
index a055384ad6..6581f4c69c 100644
--- a/Documentation/git-merge.adoc
+++ b/Documentation/git-merge.adoc
@@ -68,6 +68,7 @@ OPTIONS
 include::merge-options.adoc[]
 
 `-m <msg>`::
+`--message=<msg>`::
 	Set the commit message to be used for the merge commit (in
 	case one is created).
 +

base-commit: c69baaf57ba26cf117c2b6793802877f19738b0d
-- 
gitgitgadget

             reply	other threads:[~2026-05-29  1:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-29  1:55 Brandon Dong via GitGitGadget [this message]
2026-05-29  5:02 ` [PATCH] doc: add missing --message long option to merge docs Junio C Hamano
2026-05-31  6:37   ` Brandon

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=pull.2315.git.git.1780019726297.gitgitgadget@gmail.com \
    --to=gitgitgadget@gmail.com \
    --cc=brandondong96@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.