From: Junio C Hamano <gitster@pobox.com>
Date: Wed, 29 Jul 2020 18:16:46 GMT
Subject: Re: [PATCH] comment: fix spelling mistakes inside comments
Message-ID: <xmqq4kpqb301.fsf@gitster.c.googlers.com>
In-Reply-To: <571792b3-e65b-e6e8-34b9-56a87a47de8d@gmail.com>

Derrick Stolee <stolee@gmail.com> writes:

> I'll leave it to more experienced contributors to comment on how a
> comment-only patch fits with this section Documentation/CodingGuidelines:
>
>  - Fixing style violations while working on a real change as a
>    preparatory clean-up step is good, but otherwise avoid useless code
>    churn for the sake of conforming to the style.
>
> In my opinion, this change is not harmful, but also isn't super
> necessary. I could go either way.

Typofixes in comments has no chance of breaking things than a
carelessly done code churn made in the name of cleaning up, so
cost-benefit comparison is much more favourable.  I'm sure that I
won't be exhausted after reviewing comment-only patch as much as
after reviewing code-churn only patch.