From: Junio C Hamano <gitster@pobox.com>
To: Michael Witten <mfwitten@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/4] Typos: t/README
Date: Wed, 30 Mar 2011 11:58:34 -0700 [thread overview]
Message-ID: <7vd3l8o2p1.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <ca8eabbf-ed1b-4b46-a7f7-4b068a2de5b7-mfwitten@gmail.com> (Michael Witten's message of "Tue, 22 Feb 2011 17:15:00 +0000")
Michael Witten <mfwitten@gmail.com> writes:
> @@ -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
> -------------------------------------
A quick googling seem to indicate that both forms are accepted and widely
used (72k hits for "Do's and Don'ts" vs 45k hits for "Dos and Don'ts" in
www.google.com/books search), so I'd rather drop this hunk.
But all others are unambiguous improvements. Thanks.
next prev parent reply other threads:[~2011-03-30 18:58 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 ` [PATCH 1/4] Typos: t/README Michael Witten
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 ` Junio C Hamano [this message]
2011-03-30 19:02 ` [PATCH 1/4] Typos: t/README 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=7vd3l8o2p1.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=mfwitten@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).