[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46e4b588-d35b-ec50-ad1a-8502c2903677@synopsys.com>
Date: Wed, 22 Jun 2022 09:25:16 +0000
From: Shahab Vahedi <Shahab.Vahedi@...opsys.com>
To: Julia Lawall <julia.lawall@...ia.fr>,
Shahab Vahedi <Shahab.Vahedi@...opsys.com>
CC: Bagas Sanjaya <bagasdotme@...il.com>,
Jilin Yuan <yuanjilin@...rlc.com>,
"vgupta@...nel.org" <vgupta@...nel.org>,
"rdunlap@...radead.org" <rdunlap@...radead.org>,
"linux-snps-arc@...ts.infradead.org"
<linux-snps-arc@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ARC:mm:Fix syntax errors in comments
On 6/22/22 11:16, Julia Lawall wrote:
>
>
> On Wed, 22 Jun 2022, Shahab Vahedi wrote:
>
>> On 6/22/22 10:30, Bagas Sanjaya wrote:
>>
>>> I think that this kind of cleanup patches (typofixes) are best done
>>> as part of **actual** work on the code in question (for example
>>> refactoring or fixing build errors).
>>
>> Amen!
>
> So code that is fine will have typos forever? Fixing typos in comments
> doesn't break git blame for the following code. And typos in comments
> give a bad impression about the state of the code in general.
Of course not! Documentation is as important as the code, if not even more.
However, fixing typos to increase your commit counts to a reputable project
is not fine either. For instance, many of these proposed fixes are targeting
one single typo at a time. Couldn't they just be sent altogether!?!
--
Shahab
Powered by blists - more mailing lists