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 1kk5Bz-0003om-L6 for pgsql-docs@arkaria.postgresql.org; Tue, 01 Dec 2020 12:55:39 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kk5By-0005Od-BW for pgsql-docs@arkaria.postgresql.org; Tue, 01 Dec 2020 12:55:38 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kk5By-0005OW-5j for pgsql-docs@lists.postgresql.org; Tue, 01 Dec 2020 12:55:38 +0000 Received: from smtp.outgoing.loopia.se ([93.188.3.37]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kk5Bu-0006D8-I6 for pgsql-docs@lists.postgresql.org; Tue, 01 Dec 2020 12:55:36 +0000 Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id C566D7093F6 for ; Tue, 1 Dec 2020 13:55:28 +0100 (CET) Received: from s499.loopia.se (unknown [172.22.191.6]) by s807.loopia.se (Postfix) with ESMTP id A71912E63BAD; Tue, 1 Dec 2020 13:55:28 +0100 (CET) Received: from s474.loopia.se (unknown [172.22.191.6]) by s499.loopia.se (Postfix) with ESMTP id A1CCD1CDE906; Tue, 1 Dec 2020 13:55:28 +0100 (CET) X-Virus-Scanned: amavisd-new at amavis.loopia.se X-Spam-Flag: NO X-Spam-Score: -1 X-Spam-Level: X-Spam-Status: No, score=-1 tagged_above=-999 required=6.2 tests=[ALL_TRUSTED=-1] autolearn=disabled Received: from s500.loopia.se ([172.22.191.6]) by s474.loopia.se (s474.loopia.se [172.22.190.14]) (amavisd-new, port 10024) with UTF8LMTP id owpwbxjA7CbP; Tue, 1 Dec 2020 13:55:28 +0100 (CET) X-Loopia-Auth: user X-Loopia-User: daniel@yesql.se X-Loopia-Originating-IP: 89.255.232.193 Received: from [192.168.72.43] (customer-89-255-232-193.stosn.net [89.255.232.193]) (Authenticated sender: daniel@yesql.se) by s500.loopia.se (Postfix) with ESMTPSA id 2AC201E32DBA; Tue, 1 Dec 2020 13:55:28 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\)) Subject: Re: Consistent reference to RFCs in the documentation From: Daniel Gustafsson In-Reply-To: Date: Tue, 1 Dec 2020 13:55:27 +0100 Cc: Pg Docs Content-Transfer-Encoding: quoted-printable Message-Id: <2C7F4A07-49AA-4FAD-A152-EB9DAD07D211@yesql.se> References: <2C697878-4D01-4F06-8312-2FEDE931E973@yesql.se> To: Heikki Linnakangas X-Mailer: Apple Mail (2.3445.104.17) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk > On 1 Dec 2020, at 13:39, Heikki Linnakangas wrote: > On 05/11/2020 17:09, Daniel Gustafsson wrote: >> The attached patch adds ulinks for all >> RFC's and marks subsequent mentions as acronym to make the docs = consistent. It >> also spells all as "RFC " with a whitespace as that was the = most >> commonly used spelling (there is no RFC for how to reference to an = RFC so we're >> free to choose). >=20 > There is RFC 7322, "RFC Style Guide", Section 3.5 Citations = (https://tools.ietf.org/html/rfc7322#section-3.5). That's for the style = used in RFCs themselves. It recommends "RFC " as well. Interesting, I've looked for that more than once but failed to find that section. Thanks for pointing it out. > Pushed, thanks! Thanks! cheers ./daenil=