From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: Patrick Steinhardt <ps@pks.im>, Celeste Liu <coelacanthushex@gmail.com>
Subject: Re: [PATCH] doc: replace 3 dash with correct 2 dash in git-config(1)
Date: Mon, 26 Aug 2024 10:32:42 -0700 [thread overview]
Message-ID: <xmqqle0jjikl.fsf@gitster.g> (raw)
In-Reply-To: <xmqq34mrkxre.fsf@gitster.g> (Junio C. Hamano's message of "Mon, 26 Aug 2024 10:19:17 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> Celeste Liu <coelacanthushex@gmail.com> writes:
>
>> And is there need a new patch to fix this? Or you will fix it directly?
>>>
>>> The synopsis should lose "=<regexp>" part, as the option does not
>>> take any arguments.
>
> It is a separate documentation bug. We can fix it separately.
>
> ----- >8 --------- >8 --------- >8 -----
> Subject: git-config.1: two random small fixes
Sorry but, this is a stale subject.
Subject: git-config.1: fix --regexp description in synopsis
or something, probably.
> The synopsis says --regexp=<regexp> but the --regexp option is a
> Boolean that says "the name given is not literal, but a pattern to
> match the name".
>
> Signed-off-by: Junio C Hamano <gitster@pobox.com>
> ---
>
> diff --git c/Documentation/git-config.txt w/Documentation/git-config.txt
> index 65c645d461..1ee5c89ba2 100644
> --- c/Documentation/git-config.txt
> +++ w/Documentation/git-config.txt
> @@ -10,7 +10,7 @@ SYNOPSIS
> --------
> [verse]
> 'git config list' [<file-option>] [<display-option>] [--includes]
> -'git config get' [<file-option>] [<display-option>] [--includes] [--all] [--regexp=<regexp>] [--value=<value>] [--fixed-value] [--default=<default>] <name>
> +'git config get' [<file-option>] [<display-option>] [--includes] [--all] [--regexp] [--value=<value>] [--fixed-value] [--default=<default>] <name>
> 'git config set' [<file-option>] [--type=<type>] [--all] [--value=<value>] [--fixed-value] <name> <value>
> 'git config unset' [<file-option>] [--all] [--value=<value>] [--fixed-value] <name> <value>
> 'git config rename-section' [<file-option>] <old-name> <new-name>
prev parent reply other threads:[~2024-08-26 17:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 17:20 [PATCH] doc: replace 3 dash with correct 2 dash in git-config(1) Celeste Liu
2024-08-22 18:02 ` Junio C Hamano
2024-08-23 5:45 ` Patrick Steinhardt
2024-08-23 7:59 ` Celeste Liu
2024-08-23 8:21 ` Celeste Liu
2024-08-26 6:24 ` Patrick Steinhardt
2024-08-26 15:19 ` Junio C Hamano
2024-08-26 15:56 ` Celeste Liu
2024-08-26 17:19 ` Junio C Hamano
2024-08-26 17:31 ` [PATCH] git-config.1: --get-all description update Junio C Hamano
2024-08-26 17:32 ` Junio C Hamano [this message]
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=xmqqle0jjikl.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=coelacanthushex@gmail.com \
--cc=git@vger.kernel.org \
--cc=ps@pks.im \
/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.