Re: [Monotone-devel] Re: SCMS question - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: [Monotone-devel] Re: SCMS question
Date
Msg-id 20070223142807.GK7744@alvh.no-ip.org
Whole thread Raw
In response to Re: [Monotone-devel] Re: SCMS question  (Markus Schiltknecht <markus@bluegap.ch>)
Responses Re: [Monotone-devel] Re: SCMS question  (hendrik@topoi.pooq.com)
List pgsql-hackers
hendrik@topoi.pooq.com wrote:
> On Fri, Feb 23, 2007 at 10:42:13AM -0300, Alvaro Herrera wrote:
> > Richard Levitte - VMS Whacker wrote:
> > > In message <45DE9071.5020909@bluegap.ch> on Fri, 23 Feb 2007 07:57:53 +0100, Markus Schiltknecht
<markus@bluegap.ch>said:
 
> > > 
> > > markus> Uh, yah. But I was refering to the "lots of opinions on what
> > > markus> replacement system to use". This has not much to do with the
> > > markus> want or need (for lack of a better alternative) to stay with
> > > markus> CVS, IMO.
> > > 
> > > Oh, it's an academic discussion?  Sorry, didn't catch that.
> > 
> > It's only academic because Monotone is not ready.  As soon as it is
> > ready we will be pushing much harder.
> 
> This invites the obvious question -- in which ways in monotone not 
> ready?  Not that I'm trying to imply that monotone *is* ready, of 
> course.

Time to get the initial pull is too long, mostly.  Also, having the
policy branch stuff will be good, if nothing else because it'll mean
having 1.0 out, in turn meaning UI stability, etc.  And getting Markus'
work on the CVS import will be good too (I haven't tried converting
Postgres' entire CVS repo in a while, and that certainly is a must).

I don't think we're going to get a one-shot migration, so Cristof's work
on CVS takeover would be really nice to have so that some of us can
create an "alternative" repo and cater for those that will continue to
use CVS for a while.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: "Simon Riggs"
Date:
Subject: Re: Simple Column reordering
Next
From: Tom Lane
Date:
Subject: Re: Simple Column reordering