From: Junio C Hamano <gitster@pobox•com>
To: Eric Sunshine <sunshine@sunshineco•com>
Cc: "Jean-Noël Avila via GitGitGadget" <gitgitgadget@gmail•com>,
git@vger•kernel.org, "Jean-Noël Avila" <jn.avila@free•fr>
Subject: Re: [PATCH 2/3] doc: git-clone fix missing placeholder end carret
Date: Tue, 20 Feb 2024 15:01:39 -0800 [thread overview]
Message-ID: <xmqqh6i2loz0.fsf@gitster.g> (raw)
In-Reply-To: <CAPig+cSFK_sVZn5p3Bw12HOEF4Z99niPGMHp1Dp2w2EUjjZ4zw@mail.gmail.com> (Eric Sunshine's message of "Tue, 20 Feb 2024 17:39:48 -0500")
Eric Sunshine <sunshine@sunshineco•com> writes:
> On Tue, Feb 20, 2024 at 5:33 PM Jean-Noël Avila via GitGitGadget
> <gitgitgadget@gmail•com> wrote:
>> doc: git-clone fix missing placeholder end carret
>
> I believe you meant: s/carret/caret/
>
> In English, I think this symbol is typically called an "angle bracket".
Yes, caret is "^".
>> diff --git a/Documentation/git-clone.txt b/Documentation/git-clone.txt
>> @@ -311,7 +311,7 @@ or `--mirror` is given)
>> ---ref-format=<ref-format::
>> +--ref-format=<ref-format>::
A closing angle bracket is what is missing there. Thanks for
reading carefully.
next prev parent reply other threads:[~2024-02-20 23:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 22:32 [PATCH 0/3] Doc placeholders Jean-Noël Avila via GitGitGadget
2024-02-20 22:32 ` [PATCH 1/3] doc: git-rev-parse: enforce command-line description syntax Jean-Noël Avila via GitGitGadget
2024-02-20 22:57 ` Junio C Hamano
2024-02-21 7:41 ` Jean-Noël Avila
2024-02-21 17:31 ` Junio C Hamano
2024-02-21 21:52 ` Jean-Noël AVILA
2024-02-21 22:36 ` Junio C Hamano
2024-02-22 9:07 ` Jean-Noël AVILA
2024-02-22 16:38 ` Junio C Hamano
2024-02-24 18:28 ` Jean-Noël AVILA
2024-02-20 22:32 ` [PATCH 2/3] doc: git-clone fix missing placeholder end carret Jean-Noël Avila via GitGitGadget
2024-02-20 22:39 ` Eric Sunshine
2024-02-20 23:01 ` Junio C Hamano [this message]
2024-02-20 22:32 ` [PATCH 3/3] doc: add some missing sentence dots Jean-Noël Avila via GitGitGadget
2024-02-20 22:50 ` 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=xmqqh6i2loz0.fsf@gitster.g \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitgitgadget@gmail$(echo .)com \
--cc=jn.avila@free$(echo .)fr \
--cc=sunshine@sunshineco$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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