Tom Lane wrote:
(It might be good if we had a more standardized way of generating
HISTORY though. I tried a couple different versions of lynx and
got a couple different outputs, none perfectly matching whatever
version Bruce is using ...)
There lies the problem. Making these text files is
Are we going to regenerate the 7.4.1 tar ball?
--
Tatsuo Ishii
Peter Eisentraut - PostgreSQL wrote:
CVSROOT:/cvsroot
Module name:pgsql-server
Changes by: [EMAIL PROTECTED] 03/12/21 17:36:34
Modified files:
doc/src/sgml : Tag: REL7_4_STABLE release.sgml
Tatsuo Ishii [EMAIL PROTECTED] writes:
Are we going to regenerate the 7.4.1 tar ball?
No. There is no difference other than some trailing spaces between
what Bruce committed and what I put in yesterday.
(It might be good if we had a more standardized way of generating
HISTORY though. I tried
Marc G. Fournier [EMAIL PROTECTED] writes:
On Mon, 22 Dec 2003, Tom Lane wrote:
(It might be good if we had a more standardized way of generating
HISTORY though. I tried a couple different versions of lynx and
got a couple different outputs, none perfectly matching whatever
version Bruce is
On Mon, 22 Dec 2003, Bruce Momjian wrote:
The only problem with removing HISTORY from CVS is that we will not have
an easily reable list of release changes _until_ we package the release.
Nonsense. Point 'em to
http://developer.postgresql.org/docs/postgres/release.html
Perhaps we should
Bruce Momjian [EMAIL PROTECTED] writes:
Tom Lane wrote:
Last cycle, Peter encouraged people to add quick-and-dirty release notes
into release.sgml when important changes are made, and I thought that
worked pretty well.
Would you be more specific? How did it work well?
There was a place for
