Re: .gitignore patch for coverage builds - Mailing list pgsql-hackers

From Robert Haas
Subject Re: .gitignore patch for coverage builds
Date
Msg-id AANLkTi=x_deFj6pxouzKkMmJMcuBFOXwKvrNOGeZqAVT@mail.gmail.com
Whole thread Raw
In response to Re: .gitignore patch for coverage builds  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: .gitignore patch for coverage builds  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Jan 26, 2011 at 4:44 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> "Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
>> Building for coverage and running the reports littered my tree with
>> files which should probably be in .gitignore for just such a
>> contingency.  Patch attached.
>
> Ick.  That's an awful lot of stuff to have global ignores for.

The "coverage" directory ignore seems a little icky, but the rest
seems unlikely to pick up anything incidental.

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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: ALTER TYPE 3: add facility to identify further no-work cases
Next
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Remove arbitrary ALTER TABLE .. ADD COLUMN restriction.