Re: [PATCH 0/1] Fix two documentation typos

From: Junio C Hamano <gitster@pobox.com>
Date: Aug 5, 2019, 17:04 UTC
Message-ID: <xmqqlfw7ilxa.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <20190803235914.GA5353@sigill.intra.peff.net>

Jeff King <peff@peff.net> writes:

Show 15 quoted lines

> 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.