Greg Sabino Mullane wrote: [ There is text before PGP section. ] > > -----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.
Agreed. It is nice to have the emails numbered in arrival order, but changes to old URLs are worse. -- Bruce Momjian [EMAIL PROTECTED] EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
