Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 0A2289FA08E for ; Fri, 2 Nov 2007 13:17:49 -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 40397-06-2 for ; Fri, 2 Nov 2007 13:17:32 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from tinlc.com (unknown [72.18.206.65]) by postgresql.org (Postfix) with ESMTP id 478FE9FA0FC for ; Fri, 2 Nov 2007 13:17:23 -0300 (ADT) Received: from localhost ([127.0.0.1]) by tinlc.com with smtp (Exim 4.60) (envelope-from ) id 1InzDb-0006UJ-EW; Fri, 02 Nov 2007 11:17:59 -0500 From: "Greg Sabino Mullane" To: pgsql-www@postgresql.org Subject: Keeping things easy to find X-PGP-Key: 2529 DF6A B8F7 9407 E944 45B4 BC9B 9067 1496 4AC8 X-Request-PGP: http://www.biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 Date: Fri, 2 Nov 2007 16:17:59 -0000 X-Mailer: JoyMail 2.01 Message-ID: X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200711/62 X-Sequence-Number: 12840 -----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 This page comes up at the top of some Google searches, including "Postgresql CVS" and "Postgresql source": http://www.postgresql.org/developer/sourcecode/ However, it's 404. Can we get it redirected to the new page? A couple more suggestions: * Can we make such redirects a standard practice when we decide to rearrange our directories or rename files? * Can we parse the web server error logs to proactively find problems like this and get them fixed quickly? - -- Greg Sabino Mullane greg@turnstep.com PGP Key: 0x14964AC8 200711021215 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iD8DBQFHK01ivJuQZxSWSsgRAwAMAJ9sOmWsF+fJeWHu9534Yysby+d3PgCg/qKU ca7QjQ8rxbxTcmGaEGtt3Ms= =jFe4 -----END PGP SIGNATURE-----