Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 399789FBF4E for ; Wed, 11 Jul 2007 10:23:13 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 86315-07 for ; Wed, 11 Jul 2007 10:23:00 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from lists.commandprompt.com (unknown [207.173.203.254]) by postgresql.org (Postfix) with ESMTP id CF35A9FBF13 for ; Wed, 11 Jul 2007 10:23:09 -0300 (ADT) Received: from perhan.alvh.no-ip.org (201-221-218-82.bk12-dsl.surnet.cl [201.221.218.82]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id l6BDMrFF022427; Wed, 11 Jul 2007 06:22:55 -0700 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id EFF4847C44; Wed, 11 Jul 2007 09:22:51 -0400 (CLT) Date: Wed, 11 Jul 2007 09:22:51 -0400 From: Alvaro Herrera To: Bruce Momjian Cc: Tom Lane , Ray Stell , pgsql-admin@postgresql.org Subject: Re: 8.2.4 patches? Message-ID: <20070711132251.GD3294@alvh.no-ip.org> References: <20070711124937.GA3294@alvh.no-ip.org> <200707111306.l6BD69G14356@momjian.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200707111306.l6BD69G14356@momjian.us> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: ClamAV 0.90.3/3634/Tue Jul 10 18:14:01 2007 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (lists.commandprompt.com [192.168.2.159]); Wed, 11 Jul 2007 06:22:56 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200707/104 X-Sequence-Number: 26085 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. > 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). -- Alvaro Herrera http://www.amazon.com/gp/registry/CTMLCN8V17R4 Este mail se entrega garantizadamente 100% libre de sarcasmo.