Re: [noreply@postgresql.org: coder]
| От | Magnus Hagander |
|---|---|
| Тема | Re: [noreply@postgresql.org: coder] |
| Дата | |
| Msg-id | CABUevEwPnGxxWwojdT=VSOE2piXdXsqP+rkpWwqeddT5xEyDuQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | [noreply@postgresql.org: coder] (Bruce Momjian <bruce@momjian.us>) |
| Ответы |
Re: [noreply@postgresql.org: coder]
|
| Список | 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@momjian.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@postgresql.org> -----
Date: Mon, 19 Mar 2018 15:29:32 +0000
From: PG Doc comments form <noreply@postgresql.org>
To: pgsql-docs@lists.postgresql.org
Cc: melatti.michael@gmail.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@momjian.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 +
В списке pgsql-www по дате отправления: