From: "Nathan Stocks via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Nathan Stocks <cleancut@github.com>, Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 0/1] t: fix typo in test descriptions
Date: Wed, 06 Nov 2019 04:18:08 +0000 [thread overview]
Message-ID: <pull.448.git.1573013889.gitgitgadget@gmail.com> (raw)
Fix two test descriptions which stated "git -ls-files" when the actual
command being tested was "git ls-files".
I based this patch off of 'maint' since the typo predates the latest
release, but the patch can be applied cleanly to 'master'.
I happened to run across this while running the following quick-and-dirty
command to see if it looked like there were any undocumented top-level git
options that were run from inside tests. The answer to that was
unsurprisingly "no", but it did turn up this typo to fix!
git grep "[^./i]git -" |
grep -v 'git -C' |
grep -v 'git -c' |
grep -v 'git --help' |
grep -v 'git --exec-path' |
grep -v 'git --version' |
grep -v 'git --html-path' |
grep -v 'git --man-path' |
grep -v 'git --info-path' |
grep -v 'git -p' |
grep -v 'git --paginate' |
grep -v 'git -P' |
grep -v 'git --no-pager' |
grep -v 'git --no-replace-objects' |
grep -v 'git --bare' |
grep -v 'git --git-dir' |
grep -v 'git --work-tree' |
grep -v 'git --namespace' |
grep -v 'test_completion' |
grep -v 'git-grep.*acted as if' |
grep -v 'git --super-prefix' |
grep -v 'git --no-replace-objects' |
grep -v 'git --literal-pathspecs' |
grep -v 'git --glob-pathspecs' |
grep -v 'git --noglob-pathspecs' |
grep -v 'git --icase-pathspecs' |
grep -v 'git --no-optional-locks' |
grep -v 'git --list-cmds' |
grep -v 'git ->'
Nathan Stocks (1):
t: fix typo in test descriptions
t/t3060-ls-files-with-tree.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
base-commit: 5fa0f5238b0cd46cfe7f6fa76c3f526ea98148d9
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-448%2FCleanCut%2Ft3060-fix-description-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-448/CleanCut/t3060-fix-description-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/448
--
gitgitgadget
next reply other threads:[~2019-11-06 4:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 4:18 Nathan Stocks via GitGitGadget [this message]
2019-11-06 4:18 ` [PATCH 1/1] t: fix typo in test descriptions Nathan Stocks via GitGitGadget
2019-11-06 4:28 ` Jeff King
2019-11-06 4:45 ` Nathan Stocks
2019-11-06 7:37 ` Taylor Blau
2019-11-06 15:14 ` Nathan Stocks
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pull.448.git.1573013889.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=cleancut@github.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).