Re: [HACKERS] Re: [BUGS] First experiences with Postgresql 7.0

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Rolf Grossmann <grossman(at)securitas(dot)net>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Re: [BUGS] First experiences with Postgresql 7.0
Date: 2000-02-24 16:11:37
Message-ID: 21953.951408697@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Peter Eisentraut <e99re41(at)DoCS(dot)UU(dot)SE> writes:
>> This is arguably a bug fix, so you needn't worry about it being beta
>> phase.

> I'm not sure how this works now: Do I just commit it to the tree, so it
> will be in when, say, beta2 gets generated?

Right. No real difference in commit procedures at this point.

At some point after the release, we will set up a branch for REL_7.0,
and after that, ordinary commits will only apply to new development
for 7.1, not to the stable release branch. But no need to worry about
that for now.

> Ah, a tcsh user! ;) I could go for an -X option to suppress reading the
> startup file, with default being that it is read in any mode. A pretty
> dump option letter, but not all that far-fetched.

Works for me...

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Lamar Owen 2000-02-24 16:13:51 Re: [HACKERS] Re: [BUGS] First experiences with Postgresql 7.0
Previous Message Bruce Momjian 2000-02-24 16:08:01 Re: [HACKERS] Re: [BUGS] First experiences with Postgresql 7.0

Browse pgsql-hackers by date

  From Date Subject
Next Message Lamar Owen 2000-02-24 16:13:51 Re: [HACKERS] Re: [BUGS] First experiences with Postgresql 7.0
Previous Message Bruce Momjian 2000-02-24 16:08:01 Re: [HACKERS] Re: [BUGS] First experiences with Postgresql 7.0