Re: ideas for auto-processing patches
| От | Gavin Sherry |
|---|---|
| Тема | Re: ideas for auto-processing patches |
| Дата | |
| Msg-id | Pine.LNX.4.58.0701051221410.3624@linuxworld.com.au обсуждение исходный текст |
| Ответ на | Re: ideas for auto-processing patches (Alvaro Herrera <alvherre@commandprompt.com>) |
| Список | pgsql-hackers |
On Thu, 4 Jan 2007, Alvaro Herrera wrote: > Gavin Sherry wrote: > > On Thu, 4 Jan 2007 markwkm@gmail.com wrote: > > > > > 1. Pull source directly from repositories (cvs, git, etc.) PLM > > > doesn't really track actually scm repositories. It requires > > > directories of source code to be traversed, which are set up by > > > creating mirrors. > > > > It seems to me that a better approach might be to mirror the CVS repo -- > > or at least make that an option -- and pull the sources locally. Having to > > pull down >100MB of data for every build might be onerous to some build > > farm members. > > Another idea is using the git-cvs interoperability system, as described > here (albeit with SVN, but the idea is the same): > > http://tw.apinc.org/weblog/2007/01/03#subverting-git It seems like that will just add one more cog to the machinary for no extra benefit. Am I missing something? > > Now, if we were to use a distributed system like Monotone this sort of > thing would be completely a non-issue ... Monotone is so 2006. The new new thing is mercurial! Gavin
В списке pgsql-hackers по дате отправления: