Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1m1D0B-0001B6-LW for pgsql-docs@arkaria.postgresql.org; Wed, 07 Jul 2021 19:14:31 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1m1D0A-0008Fr-1r for pgsql-docs@arkaria.postgresql.org; Wed, 07 Jul 2021 19:14:30 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1m1D09-0008Fj-9T for pgsql-docs@lists.postgresql.org; Wed, 07 Jul 2021 19:14:29 +0000 Received: from wout4-smtp.messagingengine.com ([64.147.123.20]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1m1D06-0006Jf-0x for pgsql-docs@lists.postgresql.org; Wed, 07 Jul 2021 19:14:28 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 18F4332001AB; Wed, 7 Jul 2021 15:14:22 -0400 (EDT) Received: from imap21 ([10.202.2.71]) by compute1.internal (MEProxy); Wed, 07 Jul 2021 15:14:22 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eulerto.com; h= mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm2; bh=XUuZJCTKvmT+QL6YmNVz5Glc67Uriaq X2O5csASqvKc=; b=NnFvxdYl+0Pjgb6AsO3SuVZML5CoW5x2rkcbTGcAXLgu+DX ybkYJ7L8DzIZsOLQcg+ru2LcQB7Gg403nxLFQoINWQSKTT/z+CnLQxQ8+fIo4PZv Rb0o9ri+D1LfiiaBc0HZADmMPt0s4H2r/p4rCu0h66yK2awi8WMkJG7INF/VmuyL mLumu+MjxKxu0FDbeOD/zEaFd3qe7jd7u2wzBS+cIT5XwaI8ZkbT2yZ6qL/K9dT1 opRWKASt9PnGWVYYdk80n6CUDOpncaGNzKh8vfhNCs8GJFR7vZcrH7XSmy/cLI3m kzcpBE0CVSIQan7pykQ8sngp4eGG8jywG+SFgqg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=XUuZJC TKvmT+QL6YmNVz5Glc67UriaqX2O5csASqvKc=; b=wioZJCgTYdVz3xGKonxcW6 s2DOms4WvYa07VjMbOGB/enPdU0ET3+5kjtrHU9+sREDVywTaIb6ZkzmO9QDLJcj WuP5S6VtpKW7XJrFIJ6Gie0QEXRaqInn5QyMIHWfmrN8/QPh+Vrx0nAcLojAA70E T0Sfqpkf2wanknoE0X6x85fJi/Q8eeSJOUhSMVxqg8nzkQYM0JIpCM9LHf3+57dh CSfk+kJDczs9lcZtPAoh/l/tazmK+irMDW4AWuWtM+f5gcNppcd0LukTsL2UZSdS P4rRkVO8s9SoEu4AI18ddwUQp8U45D198ADg0tNP3IAWPOJ56J1yz1PC3Tq9vSsA == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrtddvgddufeduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesrgdtreerreertdenucfhrhhomhepfdfguhhl vghrucfvrghvvghirhgrfdcuoegvuhhlvghrsegvuhhlvghrthhordgtohhmqeenucggtf frrghtthgvrhhnpedtjeffieeuieeggeehieeutdevleetteejiedtgfehheefueekveff tedujefhffenucffohhmrghinhepphhoshhtghhrvghsqhhlrdhorhhgpdgvnhhtvghrph hrihhsvggusgdrtghomhenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgr ihhlfhhrohhmpegvuhhlvghrsegvuhhlvghrthhordgtohhm X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 3DFCA51C0060; Wed, 7 Jul 2021 15:14:21 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.5.0-alpha0-531-g1160beca77-fm-20210705.001-g1160beca Mime-Version: 1.0 Message-Id: <614588d6-77cd-4231-8da4-9ba87130e1aa@www.fastmail.com> In-Reply-To: <20210707163009.44wpfn7uc72zwyp7@localhost> References: <20210707163009.44wpfn7uc72zwyp7@localhost> Date: Wed, 07 Jul 2021 16:13:59 -0300 From: "Euler Taveira" To: rir , "Pg Docs" Subject: Re: conventions Content-Type: multipart/alternative; boundary=8224d73e802b4bbfaa00b3505a0942c5 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --8224d73e802b4bbfaa00b3505a0942c5 Content-Type: text/plain On Wed, Jul 7, 2021, at 1:30 PM, rir wrote: > > The conventions page is weak. Here is a proposed start for > change. Seeing SQL as an early language, I have tried to use something > like plain English. Here "early" could describe a mail merge user > wandering into programming SQL after seeing some simple examples. Hi Rob, Unless someone translates your suggestion into a patch, you could probably do it and submit a patch. If you are a first time contributor, I suggest that you read Submitting a patch [1]. It is a detailed document that describes the development workflow. Talking about this patch, edit doc/src/sgml/notation.sgml, run configure script, follow the steps described in Building the Documentation section [2] and send a 'git diff' to this list. You might need some tools [3] to build the documentation. [1] https://wiki.postgresql.org/wiki/Submitting_a_Patch [2] https://www.postgresql.org/docs/current/docguide-build.html [3] https://www.postgresql.org/docs/current/docguide-toolsets.html -- Euler Taveira EDB https://www.enterprisedb.com/ --8224d73e802b4bbfaa00b3505a0942c5 Content-Type: text/html Content-Transfer-Encoding: quoted-printable
On Wed, Jul 7, = 2021, at 1:30 PM, rir wrote:

The conventions page is weak.  Her= e is a proposed start for
change.  Seeing SQL as an e= arly language, I have tried to use something
like plain En= glish.  Here "early" could describe a mail merge user
wandering into programming SQL after seeing some simple examples.
Hi Rob,

Unless someon= e translates your suggestion into a patch, you could probably do
it and submit a patch. If you are a first time contributor, I sug= gest that you
read Submitting a patch [1]. It is a detaile= d document that describes the
development workflow.

Talking about this patch, edit doc/src/sgml/notat= ion.sgml, run configure
script, follow the steps described= in Building the Documentation section [2]
and send a 'git dif= f' to this list. You might need some tools [3] to build the
do= cumentation.


=


--
Euler Taveira
EDB   https://www.enterprisedb.com/

<= /body> --8224d73e802b4bbfaa00b3505a0942c5--