Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 029EE9FA5B9 for ; Wed, 11 Jul 2007 10:28:09 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 03277-03 for ; Wed, 11 Jul 2007 10:27:58 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from momjian.us (momjian.us [70.90.9.53]) by postgresql.org (Postfix) with ESMTP id C024B9FA502 for ; Wed, 11 Jul 2007 10:28:04 -0300 (ADT) Received: (from bruce@localhost) by momjian.us (8.11.6/8.11.6) id l6BDS0B18204; Wed, 11 Jul 2007 09:28:00 -0400 (EDT) From: Bruce Momjian Message-Id: <200707111328.l6BDS0B18204@momjian.us> Subject: Re: 8.2.4 patches? In-Reply-To: <20070711132251.GD3294@alvh.no-ip.org> To: Alvaro Herrera Date: Wed, 11 Jul 2007 09:28:00 -0400 (EDT) CC: Tom Lane , Ray Stell , pgsql-admin@postgresql.org X-Mailer: ELM [version 2.4ME+ PL123] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200707/105 X-Sequence-Number: 26086 Alvaro Herrera wrote: > Bruce Momjian wrote: > > Alvaro Herrera wrote: > > > Tom Lane wrote: > > > > Alvaro Herrera writes: > > > > > Ray Stell wrote: > > > > >> Are there critical security or performance patches that should be > > > > >> applied to 824 and how could I have determined this without this post? > > > > > > > > > The changelog after 8.2.4 is below. I don't think there's a way to get > > > > > this easily, short of having a copy of the CVS repository. > > > > > > > > The other way to check the change history is to troll the > > > > pgsql-committers archives > > > > http://archives.postgresql.org/pgsql-committers/ > > > > although certainly cvs2cl output is a lot easier to scan. > > > > > > > > My $0.02: if you really want the latest and greatest, the nightly > > > > snapshot tarball of the current stable branch would be the thing to > > > > grab, rather than fooling with individual patches. > > > > > > Hmm, do we include the cvs2cl-generated ChangeLog in the tarballs? > > > > No, we don't. We used to but the file got too large. > > How about including the changelog until the branch point? > > I remember there used to be ChangeLog files on CVS but that sounds a bit > redundant. But I am thinking in generating them for the tarball only, > just like we provide the HTML docs or the bison output. Yes, they were just in the tarballs. > > Perhaps we should supply a URL that generates that information. > > I think we should *also* do this. > > FWIW I use > > cvs2cl --revisions --no-indent --no-wrap --separate-header --follow $branch \ > --no-ancestors --accum > > and it generates a 90k file when branch=REL8_2_STABLE (it only includes > the changes after REL8_2_STABLE was first tagged). But then do we also supply the cvs2cl for a major release. We certainly could. -- Bruce Momjian http://momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +