git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Mark Rushakoff <mark.rushakoff@gmail.com>,
	Mark Rushakoff via GitGitGadget <gitgitgadget@gmail.com>,
	git@vger.kernel.org
Subject: Re: [PATCH 0/1] Fix two documentation typos
Date: Mon, 05 Aug 2019 10:04:01 -0700	[thread overview]
Message-ID: <xmqqlfw7ilxa.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20190803235914.GA5353@sigill.intra.peff.net> (Jeff King's message of "Sat, 3 Aug 2019 19:59:14 -0400")

Jeff King <peff@peff.net> writes:

> On Sat, Aug 03, 2019 at 07:48:20AM -0700, Junio C Hamano wrote:
>
>> > Then I noticed a "can not" and updated that and other occurrences in
>> > Documentation to cannot. The glossary sentence with "can not" was
>> > "Consequently, an object can not be changed." To me, that reads like "it is
>> 
>> Hmph, I am not a native speaker, but I have to say that this is the
>> first time I heard that "I can not drive" to mean "I have a choice
>> of not driving (even though I am capable of driving)".
> ...
> That said, I think in many error messages, "unable to" is often better
> (and we already use it quite frequently).
> ...
> ... So it is Git saying "you cannot do this", not "I was unable to
> do this". :)

Thanks.  In any case, none of the s/can not/cannot/ in Mark's patch
is making anything worse (the only case I can think of that a blind
search-and-replace would break would be a phrase like "I can not
only do X but...", but the none of the ones Mark spotted is like
that), so let's take the patch as-is for now.



      reply	other threads:[~2019-08-05 17:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-03  5:33 Mark Rushakoff via GitGitGadget
2019-08-03  5:33 ` [PATCH 1/1] doc: typo: s/can not/cannot/ and s/is does/does/ Mark Rushakoff via GitGitGadget
2019-08-03 14:48 ` [PATCH 0/1] Fix two documentation typos Junio C Hamano
2019-08-03 23:59   ` Jeff King
2019-08-05 17:04     ` Junio C Hamano [this message]

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=xmqqlfw7ilxa.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=mark.rushakoff@gmail.com \
    --cc=peff@peff.net \
    --subject='Re: [PATCH 0/1] Fix two documentation typos' \
    /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

Code repositories for project(s) associated with this 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).