From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: Peter Eisentraut <peter_e@gmx.net>
To: Marc G. Fournier <scrappy@hub.org>
To: pgsql-hackers@postgresql.org
Cc: Andrew Dunstan <andrew@dunslane.net>
Cc: Aidan Van Dyk <aidan@highrise.ca>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: PostgreSQL Developer meeting minutes up
Date: Wed, 27 May 2009 20:18:18 -0500
Message-ID: <4A1DA009.EE98.0025.1@wicourts.gov> (raw)
In-Reply-To: <306EEBC41F4E2BA856DDE879@ganymede.hub.org>
References: <4A189843.3010200@agliodbs.com>
<20090526153501.GG15213@yugib.highrise.ca>
<20090526185313.T35116@hub.org>
<200905271633.28594.peter_e@gmx.net>
<306EEBC41F4E2BA856DDE879@ganymede.hub.org>
"Marc G. Fournier" <scrappy@hub.org> wrote:
> I'm curious as to what is different about these vs all the other
> tags I've ever done, both before, and after ...
Any chance you tagged, changes were committed, and you then tagged
files from such a later commit as part of the release, or moved the
tag to the later commit? Those are perfectly reasonable things to do
under the CVS philosophy, and not in line with the philosophy of some
of the other products.
If there's a chance you did that on a couple beta releases in that
time frame, and on no others, that might explain it.
One product's flexibility is another product's "broken".
-Kevin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: Kevin.Grittner@wicourts.gov, peter_e@gmx.net, scrappy@hub.org, andrew@dunslane.net, aidan@highrise.ca, tgl@sss.pgh.pa.us
Subject: Re: PostgreSQL Developer meeting minutes up
In-Reply-To: <4A1DA009.EE98.0025.1@wicourts.gov>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox