From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | josh(at)agliodbs(dot)com, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Feature Freeze date for 8.4 |
Date: | 2007-10-24 06:57:28 |
Message-ID: | 20071024065728.GQ2333@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Oct 23, 2007 at 07:24:21PM -0400, Tom Lane wrote:
> Josh Berkus <josh(at)agliodbs(dot)com> writes:
> > Mind you, I'm in favor of one. A new SCM would make some other
> > development tasks easier. However, I'm reluctant to open the
> > can-of-worms which is the "what SCM should we use" discussion
> > again, and complicate something which we seem to have consensus
> > on.
We don't need to, as the tool is already in place.
> As near as I can tell, the arguments for a new SCM mostly apply to
> work which individual developers are doing outside the main tree.
> So, given the existence of stuff like git-cvsimport, I don't see a
> strong reason why anyone who wants to work that way can't already
> sync the core CVS with a local SCM-of-their-choice and get on with
> it.
>
> You're right that this is utterly unrelated to the scheduling
> question, anyway.
It's not even slightly unrelated. It's a way of preventing bit-rot on
large patches and keeping them in sync :)
Cheers,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2007-10-24 06:59:32 | Re: Feature Freeze date for 8.4 |
Previous Message | Simon Riggs | 2007-10-24 06:57:15 | Re: Feature Freeze date for 8.4 |