Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 101A09FA2A1 for ; Tue, 6 Feb 2007 10:27:54 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-new, port 10024) with ESMTP id 55147-03 for ; Tue, 6 Feb 2007 10:27:37 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from developer.pgadmin.org (developer.pgadmin.org [63.246.23.140]) by postgresql.org (Postfix) with ESMTP id 03ECC9FA320 for ; Tue, 6 Feb 2007 10:27:42 -0400 (AST) Received: from [172.24.32.30] ([62.232.55.118]) (authenticated bits=0) by developer.pgadmin.org (8.13.8/8.13.8) with ESMTP id l16E4K3U002310 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 6 Feb 2007 14:04:22 GMT Message-ID: <45C89059.8020801@postgresql.org> Date: Tue, 06 Feb 2007 14:27:37 +0000 From: Dave Page User-Agent: Thunderbird 1.5.0.9 (Macintosh/20061207) MIME-Version: 1.0 To: "Marc G. Fournier" CC: Tom Lane , David Fetter , Josh Berkus , pgsql-www@postgresql.org Subject: Re: How to coordinate web team for security releases? References: <200702051128.13819.josh@agliodbs.com> <20070205210315.GA7988@fetter.org> <20476.1170711517@sss.pgh.pa.us> <45C7A881.10303@postgresql.org> <366793A397285F9C94B3ABF1@ganymede.hub.org> <45C83D35.1040305@postgresql.org> <7DF491CD2B7C76C4475F75F2@ganymede.hub.org> <45C88A6F.8060500@postgresql.org> <45C88BF1.7020503@postgresql.org> <0DCBB56A11E2B896CA4C7992@ganymede.hub.org> In-Reply-To: <0DCBB56A11E2B896CA4C7992@ganymede.hub.org> X-Enigmail-Version: 0.94.1.2 OpenPGP: url=http://www.pgadmin.org/pgp/davepage.pgp Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200702/99 X-Sequence-Number: 11504 Marc G. Fournier wrote: > >>>> /view=rev\n\nLog:\nSecurity: / >>>> >>> That should do the job. >> Or not - this went straight through: > > Of course it would ... the message comes through as something like: > > view=rev\n\nLog:\nSecurity: > > the HTTP is a clickable URL ... Only 'cos your MUA renders it as a clickable link - the code that generates the email reads: my @body; push(@body, "Author: $author\n\n"); push(@body, "Date: $date\n\n"); push(@body, "New Revision: $rev\n\n"); push(@body, "Revision summary: http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/?rev=$rev&view=rev\n\n"); push(@body, "Log:\n"); push(@body, @log); push(@body, "\n"); push(@body, "\n"); Regards, Dave