Thread: Obsolete references to GBorg in documentation
Now that gborg.postgresql.org is officially dead, seems like it'd be a
good idea to update all the references to it that are in the FAQ.
There are also some references in older sections of release.sgml,
which I'm of two minds about updating --- those are historically
correct, but as links they're not of so much use anymore.
Thoughts?
regards, tom lane
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, 13 Nov 2007 21:02:06 -0500
Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Now that gborg.postgresql.org is officially dead, seems like it'd be a
> good idea to update all the references to it that are in the FAQ.
>
> There are also some references in older sections of release.sgml,
> which I'm of two minds about updating --- those are historically
> correct, but as links they're not of so much use anymore.
> Thoughts?
There are some references in the main docs too last I checked. I can
submit a patch in the next day.
Joshua D. Drake
>
> regards, tom lane
>
> ---------------------------(end of
> broadcast)--------------------------- TIP 6: explain analyze is your
> friend
>
- --
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.commandprompt.com/
UNIQUE NOT NULL
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHOmiwATb/zqfZUUQRApuMAKCdPuaEHNgpxeMPtunkjfTP5h0x7ACgpGoe
z4N2DouGfeDDbNQ8LMsAxKw=
=zUqf
-----END PGP SIGNATURE-----
"Joshua D. Drake" <jd@commandprompt.com> writes:
> Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Now that gborg.postgresql.org is officially dead, seems like it'd be a
>> good idea to update all the references to it that are in the FAQ.
>>
>> There are also some references in older sections of release.sgml,
>> which I'm of two minds about updating --- those are historically
>> correct, but as links they're not of so much use anymore.
>> Thoughts?
> There are some references in the main docs too last I checked. I can
> submit a patch in the next day.
I think I already got everything except the items mentioned above.
regards, tom lane
Tom Lane wrote: > Now that gborg.postgresql.org is officially dead, seems like it'd be a > good idea to update all the references to it that are in the FAQ. I have updated the FAQ and FAQ_DEV. > There are also some references in older sections of release.sgml, > which I'm of two minds about updating --- those are historically > correct, but as links they're not of so much use anymore. > Thoughts? Uh, if we can update them I think we should. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://postgres.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
Tom Lane wrote: > There are also some references in older sections of release.sgml, > which I'm of two minds about updating --- those are historically > correct, but as links they're not of so much use anymore. Maybe add something like " ... [later moved to http://...pgfoundry.../]" -- Peter Eisentraut http://developer.postgresql.org/~petere/
Tom Lane wrote: > Now that gborg.postgresql.org is officially dead, seems like it'd be a > good idea to update all the references to it that are in the FAQ. > > There are also some references in older sections of release.sgml, > which I'm of two minds about updating --- those are historically > correct, but as links they're not of so much use anymore. > Thoughts? I looked at the release note mention of gborg and they are generic URLs meaning they don't point to specific projects, I think we should just leave them alone (as Marc suggested). -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://postgres.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +