Re: Mailing list? was Postgress and MYSQL

From: "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>
To: Francois Suter <dba(at)paragraf(dot)ch>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Mailing list? was Postgress and MYSQL
Date: 2004-01-15 17:05:43
Message-ID: 20040115130421.M45512@ganymede.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy pgsql-general

On Thu, 15 Jan 2004, Francois Suter wrote:

> > why not use pgsql-chat, which isn't being used at all right now ... ?
> >>
> >> I would suggest that we consider forming a pgsql-competitive email
> >> list for
>
> Whatever, but using another mailing is definitely an excellent idea. I
> actually stopped reading -general recently because it got bogged down
> in yet another PostgreSQL vs MySQL debate. And the same happens to
> advocacy too, although less frequently.
>
> Then again this means that whoever moderates -general (is that you
> Marc?) would have to move PostgreSQL vs MySQL threads to the other
> mailing list whenever they crop up, otherwise any benefits will be
> lost.

actually, nobody "moderates" any of the lists, except for pgsql-www, and
that is only for subscribers ...

What it means is that those that are on this list, if they see a tangent
tread popping up, need to learn to respond to the correct list, CC'ng in
the original poster, so that subsequent responses go to the other list ...

----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy(at)hub(dot)org Yahoo!: yscrappy ICQ: 7615664

In response to

Browse pgsql-advocacy by date

  From Date Subject
Next Message Marc G. Fournier 2004-01-15 17:09:03 Re: Mailing list? was Postgress and MYSQL
Previous Message Tom Lane 2004-01-15 16:36:10 Re: Mailing list? was Postgress and MYSQL

Browse pgsql-general by date

  From Date Subject
Next Message Marc G. Fournier 2004-01-15 17:09:03 Re: Mailing list? was Postgress and MYSQL
Previous Message David Helgason 2004-01-15 17:03:37 Bytea/Large Objects/external files best practices