From: "秃头灯笼鱼 via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: 秃头灯笼鱼 <ttdlyu@163.com>
Subject: [PATCH v2 0/2] Fix the inconsistency in the description of the namespace option's parameter
Date: Thu, 11 Apr 2024 07:56:59 +0000 [thread overview]
Message-ID: <pull.1669.v2.git.git.1712822221.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.1669.git.git.1707479467028.gitgitgadget@gmail.com>
Since the parameter of the --namespace option can contain path separators \
and can be correctly parsed, I believe that --namespace=<name> in the
SYNOPSIS section should be changed to --namespace=<path> to match the
description in the OPTIONS section.
秃头灯笼鱼 (2):
doc: git.txt-Fix inconsistency param description
doc: git.txt-Change "--user-formats" to "--user-interfaces"
Documentation/git.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
base-commit: 5216f8f5c4089ec29ce49afa147434c23e0f0163
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1669%2Fttdly%2Fdoc%2Fgit.txt-v2
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1669/ttdly/doc/git.txt-v2
Pull-Request: https://github.com/git/git/pull/1669
Range-diff vs v1:
1: 28a5625f32c = 1: 28a5625f32c doc: git.txt-Fix inconsistency param description
-: ----------- > 2: af548abd004 doc: git.txt-Change "--user-formats" to "--user-interfaces"
--
gitgitgadget
next prev parent reply other threads:[~2024-04-11 7:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 11:51 [PATCH] doc: git.txt-Fix inconsistency param description 秃头灯笼鱼 via GitGitGadget
2024-04-11 7:56 ` 秃头灯笼鱼 via GitGitGadget [this message]
2024-04-11 7:57 ` [PATCH v2 1/2] " 秃头灯笼鱼 via GitGitGadget
2024-04-11 10:39 ` Martin Ågren
2024-04-11 18:09 ` Junio C Hamano
2024-04-16 6:02 ` ttdlyu
2024-04-11 7:57 ` [PATCH v2 2/2] doc: git.txt-Change "--user-formats" to "--user-interfaces" 秃头灯笼鱼 via GitGitGadget
2024-04-11 18:11 ` Junio C Hamano
2024-04-14 2:49 ` ttdlyu
2024-04-15 17:10 ` Junio C Hamano
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.1669.v2.git.git.1712822221.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=ttdlyu@163.com \
/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.