Re: ideas for auto-processing patches

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: ideas for auto-processing patches
Дата
Msg-id 26377.1168058260@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: ideas for auto-processing patches  ("Andrew Dunstan" <andrew@dunslane.net>)
Ответы Re: ideas for auto-processing patches  ("Andrew Dunstan" <andrew@dunslane.net>)
Список pgsql-hackers
"Andrew Dunstan" <andrew@dunslane.net> writes:
> Jim Nasby wrote:
>> More important, I see no reason to tie applying patches to pulling
>> from CVS. In fact, I think it's a bad idea: you want to build just
>> what's in CVS first, to make sure that it's working, before you start
>> testing any patches against it.

> Actually, I think a patch would need to be designated against a particular
> branch and timestamp, and the buildfarm member would need to "update" to
> that on its temp copy before applying the patch.

I think I like Jim's idea better: you want to find out if some other
applied patch has broken the patch-under-test, so I cannot see a reason
for testing against anything except branch tip.

There certainly is value in being able to test against a non-HEAD branch
tip, but I don't see the point in testing against a back timestamp.
        regards, tom lane


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

Предыдущее
От: "Andrew Dunstan"
Дата:
Сообщение: Re: ideas for auto-processing patches
Следующее
От: "Gurjeet Singh"
Дата:
Сообщение: Re: [PATCHES] A patch to pg_regress for Windows port