From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
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 16:00:09 |
Message-ID: | 17067.1258992009@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
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.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-11-23 16:02:24 | pgsql: Use diff's -w switch only on Windows, to avoid problems with |
Previous Message | Andrew Dunstan | 2009-11-23 15:53:49 | Re: Re: [COMMITTERS] pgsql: Remove -w (--ignore-all-space) option from pg_regress's diff |
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2009-11-23 16:02:14 | Re: Partitioning option for COPY |
Previous Message | Andrew Dunstan | 2009-11-23 15:53:49 | Re: Re: [COMMITTERS] pgsql: Remove -w (--ignore-all-space) option from pg_regress's diff |