Re: Enforce creation of destination folders for source files in pg_regress (Was: pg_regress writes into source tree)

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: Enforce creation of destination folders for source files in pg_regress (Was: pg_regress writes into source tree)
Дата
Msg-id CAB7nPqR+A-KEK7dD8QXQszXCWiAj4_88btn0GywBZzpDnE1EKA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Enforce creation of destination folders for source files in pg_regress (Was: pg_regress writes into source tree)  (Robert Haas <robertmhaas@gmail.com>)
Ответы Re: Enforce creation of destination folders for source files in pg_regress (Was: pg_regress writes into source tree)
Список pgsql-hackers
Дерево обсуждения


On Mon, Feb 23, 2015 at 9:31 PM, Robert Haas <robertmhaas@gmail.com> wrote:

> 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?

That's mainly a matter of code maintenance style (and I am on the side that a minimum number of folders in a git tree makes things easier to follow), and IMO it is strange to not have some flexibility. Btw, the reason why this patch exists is this thread of last December:
http://www.postgresql.org/message-id/flat/20141212134508.GT1768@alvh.no-ip.org#20141212134508.GT1768@alvh.no-ip.org
--
Michael

В списке pgsql-hackers по дате отправления: