From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> |
Cc: | markwkm(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org, andrew(at)dunslane(dot)net |
Subject: | Re: ideas for auto-processing patches |
Date: | 2007-01-05 01:19:49 |
Message-ID: | 20070105011949.GF3792@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Gavin Sherry wrote:
> On Thu, 4 Jan 2007 markwkm(at)gmail(dot)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
Now, if we were to use a distributed system like Monotone this sort of
thing would be completely a non-issue ...
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Gavin Sherry | 2007-01-05 01:24:23 | Re: ideas for auto-processing patches |
Previous Message | Simon Riggs | 2007-01-05 00:54:45 | Re: Tabs or Spaces |