Re: Re: [COMMITTERS] pgsql: Remove -w (--ignore-all-space) option from pg_regress's diff

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: [COMMITTERS] pgsql: Remove -w (--ignore-all-space) option from pg_regress's diff
Date: 2009-11-23 17:44:02
Message-ID: 4B0AC9E2.4010308@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>
>> Tom Lane wrote:
>>
>>> I'm thinking that the most appropriate fix is to have pg_regress
>>> continue to use -w, but only on Windows.
>>>
>
>
>> Well, the filter could be as simple as something like this in the
>> Makefile for the mingw case:
>>
>
>
>> perl -spi.bak -e 's/(?<!\r)\n$/\r\n/;' expected/*.out
>> rm expected/*.bak
>>
>
> I'm not at all thrilled with having the build process intentionally
> modify source files. Quite aside from messing up the file timestamps,
> what if this is done on a committer's machine? If the checked-out
> files didn't have CRs, that means his CVS client didn't add them
> and probably won't remove them on checkin.
>
>
>

OK, it's a choice of evils. I'm not that unhappy with what you've done.

cheers

andrew

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message User Okbob 2009-11-23 18:08:21 orafce - orafce: lock aggregates on 8.3 and older - security reasons
Previous Message Tom Lane 2009-11-23 16:02:24 pgsql: Use diff's -w switch only on Windows, to avoid problems with

Browse pgsql-hackers by date

  From Date Subject
Next Message Caleb Cushing 2009-11-23 17:50:19 Re: named generic constraints [feature request]
Previous Message Teodor Sigaev 2009-11-23 17:44:01 KNNGiST for knn-search