Re: Duplicat-word typos in code comments - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: Duplicat-word typos in code comments
Date
Msg-id 64684EA9-3BDB-413E-B254-8EA8AE2EC6DF@yesql.se
Whole thread Raw
In response to Re: Duplicat-word typos in code comments  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Duplicat-word typos in code comments  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> On 4 Oct 2021, at 15:56, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> I used to think it was better to go ahead and manually reflow, if you
> use an editor that makes that easy.  That way there are fewer commits
> touching any one line of code, which is good when trying to review
> code history.  However, now that we've got the ability to make "git
> blame" ignore pgindent commits, maybe it's better to leave that sort
> of mechanical cleanup to pgindent, so that the substantive patch is
> easier to review.

Yeah, that's precisely why I did it.  Since we can skip over pgindent sweeps it
makes sense to try and minimize such changes to make code archaeology easier.
There are of course cases when the result will be such an eyesore that we'd
prefer to have it done sooner, but in cases like these where line just got one
word shorter it seemed an easy choice.

--
Daniel Gustafsson        https://vmware.com/




pgsql-hackers by date:

Previous
From: Jaime Casanova
Date:
Subject: RfC entries in CF 2021-09
Next
From: Victor Spirin
Date:
Subject: Re: Atomic rename feature for Windows.