Re: Enforce creation of destination folders for source files in pg_regress (Was: pg_regress writes into source tree) - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Enforce creation of destination folders for source files in pg_regress (Was: pg_regress writes into source tree)
Date
Msg-id 97297339-EB70-4552-9A51-26312FFB60CC@gmail.com
Whole thread Raw
In response to Re: Enforce creation of destination folders for source files in pg_regress (Was: pg_regress writes into source tree)  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: Enforce creation of destination folders for source files in pg_regress (Was: pg_regress writes into source tree)
List pgsql-hackers
> On Feb 22, 2015, at 5:41 AM, Michael Paquier <michael.paquier@gmail.com> wrote:
> This is up to the maintainer of each extension to manage their code
> tree. However I can imagine that some people would be grateful if we
> allow them to not need sql/ and expected/ containing only one single
> .gitignore file ignoring everything with "*", making the code tree of
> their extensions cleaner.

I don't see this as an improvement. What's wrong with a .gitignore file ignoring everything?

...Robert


pgsql-hackers by date:

Previous
From: Kohei KaiGai
Date:
Subject: Re: Parallel Seq Scan
Next
From: Marko Tiikkaja
Date:
Subject: ERROR: cannot GetMultiXactIdMembers() during recovery