Обсуждение: Patch queue permenent URLs
I have found a way to have permanent URLs that stay permanent even if the email is moved from the patches queue to the patches_hold queue. The trick is to use <base> to specify the base directory in the html. The new URLs look like: http://momjian.us/mhonarc/message-id/44DA31B1.3090700@enterprisedb.com.html The new URLs appear now. The old permanent will also remain active until the next commit fest. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
On Thu, 2008-03-27 at 11:18 -0400, Bruce Momjian wrote: > The new URLs look like: > > http://momjian.us/mhonarc/message-id/44DA31B1.3090700@enterprisedb.com.html > > The new URLs appear now. The old permanent will also remain active > until the next commit fest. If they are going to be "permanent" then they should reference a PostgreSQL project domain rather than a personal domain and a company one. Without disrespect to either, our emails should not rely on external domains. That way the project is in control, not the other way around. -- Simon Riggs 2ndQuadrant http://www.2ndQuadrant.com PostgreSQL UK 2008 Conference: http://www.postgresql.org.uk
Simon Riggs wrote: > On Thu, 2008-03-27 at 11:18 -0400, Bruce Momjian wrote: > > > The new URLs look like: > > > > http://momjian.us/mhonarc/message-id/44DA31B1.3090700@enterprisedb.com.html > > > > The new URLs appear now. The old permanent will also remain active > > until the next commit fest. > > If they are going to be "permanent" then they should reference a > PostgreSQL project domain rather than a personal domain and a company > one. Without disrespect to either, our emails should not rely on > external domains. That way the project is in control, not the other way > around. Well, the patch queue maintained by Bruce has always been in his domain. And regarding "the company domain", I note that that string is part of a Message-Id, generated by the patch submitter's machine, so entirely out of Bruce's (or anyone else's) control. Note that we will have permanent URLs by Message-Id in our archives soon too: if I have my way, they will look like http://archives.postgresql.org/msgid/44DA31B1.3090700@enterprisedb.com or something similar. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support
On Thu, Mar 27, 2008 at 3:44 PM, Simon Riggs <simon@2ndquadrant.com> wrote: > On Thu, 2008-03-27 at 11:18 -0400, Bruce Momjian wrote: > > > The new URLs look like: > > > > http://momjian.us/mhonarc/message-id/44DA31B1.3090700@enterprisedb.com.html > > > > The new URLs appear now. The old permanent will also remain active > > until the next commit fest. > > If they are going to be "permanent" then they should reference a > PostgreSQL project domain rather than a personal domain and a company > one. Without disrespect to either, our emails should not rely on > external domains. That way the project is in control, not the other way > around. The company domain is from the message id by the looks of it - it should not be changed under any circumstances. -- Dave Page EnterpriseDB UK Ltd: http://www.enterprisedb.com PostgreSQL UK 2008 Conference: http://www.postgresql.org.uk
Dave Page wrote: > On Thu, Mar 27, 2008 at 3:44 PM, Simon Riggs <simon@2ndquadrant.com> wrote: > > On Thu, 2008-03-27 at 11:18 -0400, Bruce Momjian wrote: > > > > > The new URLs look like: > > > > > > http://momjian.us/mhonarc/message-id/44DA31B1.3090700@enterprisedb.com.html > > > > > > The new URLs appear now. The old permanent will also remain active > > > until the next commit fest. > > > > If they are going to be "permanent" then they should reference a > > PostgreSQL project domain rather than a personal domain and a company > > one. Without disrespect to either, our emails should not rely on > > external domains. That way the project is in control, not the other way > > around. > > The company domain is from the message id by the looks of it - it > should not be changed under any circumstances. Yep, the only way we can get rid of the company is to use an MD5 hash (which is what I used at first) instead of the message id, but people didn't like that. I have updated the permanent URL to be in the postgresql.org domain: http://momjian.postgresql.org/mhonarc/message-id/45E9ABDB.908@commandprompt.com.html Of course, momjian.us works too. (I am redirecting momjian.postgresql.org to momjian.us because the comments are bound to the domain name momjian.us.) -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. +