From: Junio C Hamano <gitster@pobox.com>
To: Danny Lin <danny0838@gmail.com>
Cc: git develop <git@vger.kernel.org>
Subject: Re: [PATCH] Revise supported options for --message in subtree doc.
Date: Mon, 17 Aug 2020 09:47:19 -0700 [thread overview]
Message-ID: <xmqq4kp143u0.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <20200815023247.788-1-danny0838@gmail.com> (Danny Lin's message of "Sat, 15 Aug 2020 10:32:47 +0800")
Danny Lin <danny0838@gmail.com> writes:
> Subject: Re: [PATCH] Revise supported options for --message in subtree doc.
Documentation/SubmittingPatches:[[summary-section]]
> Revise the documentation and remove previous "unsure" after making sure
> that --message supports only 'add', 'merge', 'pull', and 'split --rejoin'.
>
> Signed-off-by: Danny Lin <danny0838@gmail.com>
> ---
> contrib/subtree/git-subtree.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/contrib/subtree/git-subtree.txt b/contrib/subtree/git-subtree.txt
> index 352deda69d..9ccd431c7f 100644
> --- a/contrib/subtree/git-subtree.txt
> +++ b/contrib/subtree/git-subtree.txt
> @@ -139,7 +139,7 @@ OPTIONS
>
> -m <message>::
> --message=<message>::
> - This option is only valid for add, merge and pull (unsure).
> + This option is only valid for add, merge, pull, and split --rejoin.
> Specify <message> as the commit message for the merge commit.
next prev parent reply other threads:[~2020-08-17 16:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-14 14:53 [PATCH] Remove "unsure" for --message in subtree doc Danny Lin
2020-08-14 17:50 ` Junio C Hamano
2020-08-15 2:31 ` Danny Lin
2020-08-15 2:32 ` [PATCH] Revise supported options " Danny Lin
2020-08-17 16:47 ` Junio C Hamano [this message]
2020-08-18 5:21 ` [PATCH] contrib/subtree: fix "unsure" for --message in the document Danny Lin
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=xmqq4kp143u0.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=danny0838@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).