Re: Wrong digest instructions

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Herouth Maoz <herouth(at)tippcom(dot)co(dot)il>
Cc: PostgreSQL www <pgsql-www(at)postgresql(dot)org>
Subject: Re: Wrong digest instructions
Date: 2007-02-03 13:19:04
Message-ID: 45C48BC8.6090705@hagander.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

Herouth Maoz wrote:
> In http://archives.postgresql.org/pgsql-general/, there is a paragraph
> explaining how to subscribe to pgsql-general in digest mode. The
> paragraph says:
>
> If you hate getting many mail messages per day then you should consider
> a digest (where you receive multiple messages to the list as one message
> to you). To subscribe or unsubscribe from the digested list, send mail
> to majordomo(at)postgresql(dot)org <mailto:majordomo(at)postgresql(dot)org>. The body
> of the message should contain the single line "subscribe-digest
> pgsql-general" or "unsubscribe-digest pgsql-general"
>
> These instructions are wrong. I tried that and got an error from
> majordomo. Looking at the majordomo help, the proper subscription
> command is:
>
> subscribe-set pgsql-general digest
>
> Unsubscribe shouldn't be different from plain format unsubscribe.
>
> Please change the page to reflect this.

Thanks for reporting, this information is indeed incorrect.

Looking around, it's equally incorrect for all our lists.

Does anybody know where those pages are generated from? I can see the
page is autogenerated, so just changing the page will go away when it
regens, but where is the source?

Speaking of which, I think it'd be a good idea if someone who knows
which parts of the archives stuff are code and which are generated could
add the usable parts to the pgweb cvs, so we can track changes here.
Dave, I think that means you? ;-)

//Magnus

Responses

Browse pgsql-www by date

  From Date Subject
Next Message Josh Berkus 2007-02-03 19:33:47 Get ready for new minor version monday
Previous Message Magnus Hagander 2007-02-03 13:13:57 Re: Empty support page needs a redirect