Re: Enforce creation of destination folders for source files in pg_regress (Was: pg_regress writes into source tree)
В списке pgsql-hackers по дате отправления:
| От | Peter Eisentraut |
|---|---|
| Тема | Re: Enforce creation of destination folders for source files in pg_regress (Was: pg_regress writes into source tree) |
| Дата | |
| Msg-id | 54E9EF0C.3070408@gmx.net обсуждение |
| Ответ на | 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>) |
| Ответы |
Re: Enforce creation of destination folders for source
files in pg_regress (Was: pg_regress writes into source tree)
|
| Список | pgsql-hackers |
On 2/22/15 5:41 AM, Michael Paquier wrote: >> You could argue that these .gitignore files don't actually belong there, >> but your patch doesn't change or move those files, and even modules that >> have non-empty sql/ or expected/ directories have .gitignore files >> there, so it is considered the appropriate location. > > 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 would like to have an extension in tree that also does this, so we have a regression test of this functionality.
В списке pgsql-hackers по дате отправления:
Сайт использует файлы cookie для корректной работы и повышения удобства. Нажимая кнопку «Принять» или продолжая пользоваться сайтом, вы соглашаетесь на их использование в соответствии с Политикой в отношении обработки cookie ООО «ППГ», в том числе на передачу данных из файлов cookie сторонним статистическим и рекламным службам. Вы можете управлять настройками cookie через параметры вашего браузера