git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Josh Heinrichs <joshiheinrichs@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/1] git-config.1: remove value from positional args in unset usage
Date: Tue, 8 Oct 2024 14:37:34 +0200	[thread overview]
Message-ID: <ZwUnhPbpwtA1MM34@pks.im> (raw)
In-Reply-To: <20241008040749.69801-2-joshiheinrichs@gmail.com>

On Mon, Oct 07, 2024 at 10:07:49PM -0600, Josh Heinrichs wrote:
> A single positional argument appears to be enforcecd at
> builtin/config.c:993. Values need to be provided via --value.

Good catch!

Two comments regarding the commit message:

  - You are missing the Signed-off-by tag.

  - Our commit messages are typically structured such that they first
    give an observation of the issue and why it is an issue, followed by
    a proposed solution and imperative instructions for the code to
    become so.

So something like the following:

  The synopsis for the `git config unset` command mentions two
  positional arguments `<name>` and `<value>`. While the first
  positional argument is indeed correct, the second one is not. Instead,
  users are expected to pass in the value via the `--value=<value>`
  option.

  Remove the positional argument. The `--value=<value>` option is
  already documented correctly, so this is all we need to do to fix up
  the documentation.

Other than that the change looks good to me, thanks!

Patrick

  reply	other threads:[~2024-10-08 12:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-08  4:07 [PATCH 0/1] Remove value from positional args in config unset usage Josh Heinrichs
2024-10-08  4:07 ` [PATCH 1/1] git-config.1: remove value from positional args in " Josh Heinrichs
2024-10-08 12:37   ` Patrick Steinhardt [this message]
2024-10-08 14:29 ` [PATCH v2 0/1] Remove value from position args in config " Josh Heinrichs
2024-10-08 14:29   ` [PATCH v2 1/1] git-config.1: remove value from positional args in " Josh Heinrichs
2024-10-08 18:20     ` Junio C Hamano
2024-10-09  3:37       ` Patrick Steinhardt

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=ZwUnhPbpwtA1MM34@pks.im \
    --to=ps@pks.im \
    --cc=git@vger.kernel.org \
    --cc=joshiheinrichs@gmail.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 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).