From: Jeff King <peff@peff.net>
To: Evan Gates <evan.gates@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-config: fix misworded --type=path explanation
Date: Sat, 16 Sep 2023 02:16:04 -0400 [thread overview]
Message-ID: <20230916061604.GA628367@coredump.intra.peff.net> (raw)
In-Reply-To: <20230915202610.21206-1-evan.gates@gmail.com>
On Fri, Sep 15, 2023 at 02:24:59PM -0600, Evan Gates wrote:
> When `--type=<type>` was added as a prefered alias for `--<type>`
> the explanation for the path type was reworded. Whereas the previous
> explanation said "expand a leading `~`" this was changed to "adding a
> leading `~`". Change "adding" to "expanding" to correctly explain the
> canonicalization.
Yeah, the sentence as-is does not make any sense. Your suggested wording
looks good to me. Thanks.
-Peff
next prev parent reply other threads:[~2023-09-16 6:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 20:24 [PATCH] git-config: fix misworded --type=path explanation Evan Gates
2023-09-16 6:16 ` Jeff King [this message]
2023-09-16 17:45 ` 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=20230916061604.GA628367@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=evan.gates@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).