Re: ideas for auto-processing patches
От | Andrew Dunstan |
---|---|
Тема | Re: ideas for auto-processing patches |
Дата | |
Msg-id | 4078.24.211.165.134.1167968081.squirrel@www.dunslane.net обсуждение исходный текст |
Ответ на | Re: ideas for auto-processing patches (Gavin Sherry <swm@linuxworld.com.au>) |
Ответы |
Re: ideas for auto-processing patches
Re: ideas for auto-processing patches |
Список | pgsql-hackers |
Gavin Sherry wrote: > > With PLM, you could test patches against various code branches. I'd > guessed Mark would want to provide this capability. Pulling branches from > anonvcvs regularly might be burdensome bandwidth-wise. So, like you say, a > local mirror would be beneficial for patch testing. I think you're missing the point. Buildfarm members already typically have or can get very cheaply a copy of each branch they build (HEAD and/or REL*_*_STABLE). As long as the patch feed is kept to just patches which they can apply there should be no great bandwidth issues. > >> The patches would need to be vetted first, or no sane buildfarm owner >> will >> want to use them. > > It would be nice if there could be a class of trusted users whose patches > would not have to be vetted. > > Beyond committers? cheers andrew
В списке pgsql-hackers по дате отправления: