From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | PostgreSQL www <pgsql-www(at)postgresql(dot)org>, melatti(dot)michael(at)gmail(dot)com |
Subject: | Re: [noreply@postgresql.org: coder] |
Date: | 2018-04-03 14:50:17 |
Message-ID: | CABUevEwPnGxxWwojdT=VSOE2piXdXsqP+rkpWwqeddT5xEyDuQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
People creating an account, then logging in, and then submitting just one
word. That's at least the technical reason for it.
Here's a thought: trap *all* documentation comments in moderation, and have
the moderators sort things out before they are posted.
Today we can't efficiently do it based on sender, due to having the noreply
sender. But we could trap *all* of them based on regexp.
//Magnus
On Tue, Apr 3, 2018 at 4:46 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>
> Does anyone know why our documentation comments are often just one word?
> What is causing this?
>
> ------------------------------------------------------------
> ---------------
>
> ----- Forwarded message from PG Doc comments form <noreply(at)postgresql(dot)org>
> -----
>
> Date: Mon, 19 Mar 2018 15:29:32 +0000
> From: PG Doc comments form <noreply(at)postgresql(dot)org>
> To: pgsql-docs(at)lists(dot)postgresql(dot)org
> Cc: melatti(dot)michael(at)gmail(dot)com
> Subject: coder
>
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/10/static/cube.html
> Description:
>
> student
>
>
> ----- End forwarded message -----
>
> --
> Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
> EnterpriseDB http://enterprisedb.com
>
> + As you are, so once was I. As I am, so you will be. +
> + Ancient Roman grave inscription +
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Christophe Pettus | 2018-04-03 14:53:36 | Re: [noreply@postgresql.org: coder] |
Previous Message | Bruce Momjian | 2018-04-03 14:46:55 | [noreply@postgresql.org: coder] |