Re: Feature Freeze date for 8.4

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: "Martijn van Oosterhout" <kleptog(at)svana(dot)org>
Cc: "David Fetter" <david(at)fetter(dot)org>, "Chris Browne" <cbbrowne(at)acm(dot)org>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Feature Freeze date for 8.4
Date: 2007-10-24 13:12:16
Message-ID: 87ve8wsllb.fsf@oxford.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Martijn van Oosterhout" <kleptog(at)svana(dot)org> writes:

> On Tue, Oct 23, 2007 at 02:39:43PM -0700, David Fetter wrote:
>> The one below is already available, so we don't have to do a "flag
>> day" with it.
>>
>> http://repo.or.cz/w/PostgreSQL.git
>
> As someone who hasn't used GIT: if I have a modified CVS tree from some time
> back (>1 year) can I use this to manage the bitrot? Just doing a CVS
> update will probably just mark everything conflicted, so I'm wondering
> is GIT can do it better.

Well it could except not here where the git repository is being fed from CVS.
CVS is just not gathering a lot of the information that helps git and the
other distributed systems do their job. Namely it has no idea which changes
were committed together as part of the same patch, and it has no idea where
those changes came from and whether they're also in your tree.

--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Germán Poó-Caamaño 2007-10-24 13:14:45 Re: Feature Freeze date for 8.4
Previous Message Tom Lane 2007-10-24 13:07:17 Re: VACUUM always makes all pages dirty