-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>> http://archives.postgresql.org/pgsql-www/2006-07/msg00061.php > > Yeah. I think the TODO item is intended to point to what is now > http://archives.postgresql.org/pgsql-hackers/2006-02/msg00163.php > or one of the earlier messages in that thread. This is a very ugly problem. Note that there are also URLs that cannot be changed, such as older messages that point to archive posts, and many places on the web outside of our control. Why can't we just write a script that creates new numbers as needed, such as msg00163.1.php and msg00163.2.php? As far as I can tell, there is nothing magical about the naming schema itself that would cause such URLs to break anything. - -- Greg Sabino Mullane [EMAIL PROTECTED] PGP Key: 0x14964AC8 200607170743 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iD8DBQFEu3iovJuQZxSWSsgRAqafAKD51/vpiZnDkHyCQ2TrPkPEXPUQbwCfVRux 5Rw14QzglcYed2A54IGtKrc= =hz49 -----END PGP SIGNATURE----- ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
