Re: ideas for auto-processing patches - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: ideas for auto-processing patches
Date
Msg-id 20070105011949.GF3792@alvh.no-ip.org
Whole thread Raw
In response to Re: ideas for auto-processing patches  (Gavin Sherry <swm@linuxworld.com.au>)
Responses Re: ideas for auto-processing patches  (Gavin Sherry <swm@linuxworld.com.au>)
List pgsql-hackers
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

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.


pgsql-hackers by date:

Previous
From: "Simon Riggs"
Date:
Subject: Re: Tabs or Spaces
Next
From: Gavin Sherry
Date:
Subject: Re: ideas for auto-processing patches