Re: Header and comments describing routines in incorrect shape in visibilitymap.c

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Header and comments describing routines in incorrect shape in visibilitymap.c
Date: 2016-07-13 19:29:32
Message-ID: CA+TgmobXMBDENgCPvYSnpN2rGSy823qOYj4gVV-zp0eDPo37Kg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jul 8, 2016 at 7:14 AM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
>> OK, that removes comment duplication. Also, what about replacing
>> "bit(s)" by "one or more bits" in the comment terms where adapted?
>> That's bikeshedding, but that's what this patch is about.
>
> Translating my thoughts into code, I get the attached.

Seems reasonable, but is the last hunk a whitespace-only change?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2016-07-13 19:34:24 Re: pgbench - allow to store select results into variables
Previous Message Peter Geoghegan 2016-07-13 19:28:10 Re: Bug in batch tuplesort memory CLUSTER case (9.6 only)