From: Marc Strapetz <marc.strapetz@syntevo.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Marc Strapetz via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] t/README: fix typo
Date: Thu, 6 Jan 2022 07:17:42 +0100 [thread overview]
Message-ID: <b265de46-9ccd-4f31-d51c-1df1b39606d5@syntevo.com> (raw)
In-Reply-To: <9f74fc04-ea68-6bdd-3341-ecf7a2aed6cd@syntevo.com>
On 05/01/2022 17:47, Marc Strapetz wrote:
> Hi Dscho,
>
> On 05/01/2022 17:22, Johannes Schindelin wrote:
>>> @@ -466,7 +466,7 @@ explicitly providing repositories when accessing
>>> submodule objects is
>>> complete or needs to be abandoned for whatever reason (in which
>>> case the
>>> migrated codepaths still retain their performance benefits).
>>>
>>> -GIT_TEST_REQUIRE_PREREQ=<list> allows specifying a space speparated
>>> list of
>>> +GIT_TEST_REQUIRE_PREREQ=<list> allows specifying a space separated
>>> list of
>>
>> Good find!
>>
>> I'm curious, how did you find it? If it was a spell checker, did it also
>
> I found it by plain reading :) as I had troubles to get a test working.
>
> > find the "dotsh" typo in the same file (it should be "dots", I think)?
>
> I wouldn't have noticed that, but I agree that it should be
> "test_name_without_dots".
Please disregard my last statement. "test_name_without_dotsh" means
"test name without .sh extension". For
"t2109-update-index-index-version.sh", the directory will be "trash
directory.t2109-update-index-index-version".
-Marc
next prev parent reply other threads:[~2022-01-06 6:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 23:17 [PATCH] t/README: fix typo Marc Strapetz via GitGitGadget
2022-01-05 16:22 ` Johannes Schindelin
2022-01-05 16:47 ` Marc Strapetz
2022-01-06 6:17 ` Marc Strapetz [this message]
2022-01-06 17:48 ` Junio C Hamano
2022-01-05 20:41 ` 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=b265de46-9ccd-4f31-d51c-1df1b39606d5@syntevo.com \
--to=marc.strapetz@syntevo.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@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).