From: Michael Witten <mfwitten@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: [PATCH 1/4] Typos: t/README
Date: Tue, 22 Feb 2011 17:15:00 +0000 [thread overview]
Message-ID: <ca8eabbf-ed1b-4b46-a7f7-4b068a2de5b7-mfwitten@gmail.com> (raw)
In-Reply-To: <1fbceaa8-398c-44ec-8833-a03e4cca6805-mfwitten@gmail.com>
Signed-off-by: Michael Witten <mfwitten@gmail.com>
---
t/README | 11 +++++------
1 files changed, 5 insertions(+), 6 deletions(-)
diff --git a/t/README b/t/README
index ccf6a53..39408b4 100644
--- a/t/README
+++ b/t/README
@@ -201,7 +201,7 @@ we are testing.
If you create files under t/ directory (i.e. here) that is not
the top-level test script, never name the file to match the above
pattern. The Makefile here considers all such files as the
-top-level test script and tries to run all of them. A care is
+top-level test script and tries to run all of them. Care is
especially needed if you are creating a common test library
file, similar to test-lib.sh, because such a library file may
not be suitable for standalone execution.
@@ -248,7 +248,7 @@ This test harness library does the following things:
consistently when command line arguments --verbose (or -v),
--debug (or -d), and --immediate (or -i) is given.
-Do's, don'ts & things to keep in mind
+Dos, don'ts & things to keep in mind
-------------------------------------
Here are a few examples of things you probably should and shouldn't do
@@ -285,9 +285,8 @@ Do:
- Check the test coverage for your tests. See the "Test coverage"
below.
- Don't blindly follow test coverage metrics, they're a good way to
- spot if you've missed something. If a new function you added
- doesn't have any coverage you're probably doing something wrong,
+ Don't blindly follow test coverage metrics; if a new function you added
+ doesn't have any coverage, then you're probably doing something wrong,
but having 100% coverage doesn't necessarily mean that you tested
everything.
@@ -431,7 +430,7 @@ library for your script to use.
- test_tick
Make commit and tag names consistent by setting the author and
- committer times to defined stated. Subsequent calls will
+ committer times to defined state. Subsequent calls will
advance the times by a fixed amount.
- test_commit <message> [<filename> [<contents>]]
--
1.7.4.18.g68fe8
next prev parent reply other threads:[~2011-03-30 17:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 16:13 [PATCH 0/4] Miscellaneous Improvements Michael Witten
2011-02-22 17:15 ` Michael Witten [this message]
2011-02-15 23:12 ` [PATCH 2/4] Clean: Remove superfluous strbuf 'docs' Michael Witten
2011-03-02 15:25 ` [PATCH 3/4] Clean: Remove unnecessary `\' (line continuation) Michael Witten
2011-02-11 17:48 ` [PATCH 4/4] Clean: Remove useless parameters from both get_commit_info() functions Michael Witten
2011-03-30 19:21 ` [PATCH 3/4] Clean: Remove unnecessary `\' (line continuation) Junio C Hamano
2011-03-30 18:58 ` [PATCH 1/4] Typos: t/README Junio C Hamano
2011-03-30 19:02 ` Michael Witten
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=ca8eabbf-ed1b-4b46-a7f7-4b068a2de5b7-mfwitten@gmail.com \
--to=mfwitten@gmail.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.
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).