Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id CCBA49F9837 for ; Fri, 2 Nov 2007 18:47:26 -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 97489-10 for ; Fri, 2 Nov 2007 18:47:10 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from svr2.hagander.net (svr2.hagander.net [88.198.128.226]) by postgresql.org (Postfix) with ESMTP id AEE0E9FA18C for ; Fri, 2 Nov 2007 18:47:12 -0300 (ADT) Received: from dynamic.hagander.net ([127.0.0.1]) (encrypted and authenticated) by svr2.hagander.net (Postfix) with ESMTP id F3DF9DCCA1C; Fri, 2 Nov 2007 22:47:10 +0100 (CET) Message-ID: <472B9AEB.7070205@hagander.net> Date: Fri, 02 Nov 2007 22:47:23 +0100 From: Magnus Hagander User-Agent: Thunderbird 2.0.0.6 (X11/20070728) MIME-Version: 1.0 To: Greg Sabino Mullane CC: pgsql-www@postgresql.org Subject: Re: Keeping things easy to find References: In-Reply-To: X-Enigmail-Version: 0.95.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200711/66 X-Sequence-Number: 12844 Greg Sabino Mullane wrote: > > 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? Done. Will be up on next sync as usual. > A couple more suggestions: > > * Can we make such redirects a standard practice when we > decide to rearrange our directories or rename files? Makes sense. > * Can we parse the web server error logs to proactively find > problems like this and get them fixed quickly? That's probably a good idea as well, though I haven't done it yet :) Know any ready-made tools that does that, or do we break out the good ole perl interpreter? //Magnus