Re: Project scheduling issues (was Re: Per tuple overhead, cmin, cmax, OID)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Marc G(dot) Fournier" <scrappy(at)hub(dot)org>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Manfred Koizar <mkoi-pg(at)aon(dot)at>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Project scheduling issues (was Re: Per tuple overhead, cmin, cmax, OID)
Date: 2002-06-09 16:35:29
Message-ID: 6041.1023640529@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Marc G. Fournier" <scrappy(at)hub(dot)org> writes:
> Agreed on all accounts ... which is why this time, I want to do a proper
> branch when beta starts ... hell, from what I've seen suggested here so
> far, we have no choice ... At least then we can 'rip out' something from
> the beta tree without having to remove and re-add it to the development
> one later, hoping that they're changes haven't been affected by someone
> else's ...

Well, let's give that a try and see how it goes. I'm a bit worried
about the amount of double-patching we'll have to do, but other projects
seem to manage to cope with multiple active branches...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-06-09 19:58:18 Re: tuplesort: unexpected end of data
Previous Message Tom Lane 2002-06-09 16:30:21 Re: Timestamp/Interval proposals: Part 2