Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h8YRx-0001Z0-Ny for pgsql-hackers@arkaria.postgresql.org; Mon, 25 Mar 2019 22:52:14 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1h8YRw-0001mu-HE for pgsql-hackers@arkaria.postgresql.org; Mon, 25 Mar 2019 22:52:12 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h8YRv-0001mn-RU for pgsql-hackers@lists.postgresql.org; Mon, 25 Mar 2019 22:52:12 +0000 Received: from anastigmatix.net ([68.171.219.55]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h8YRt-0006br-Ev for pgsql-hackers@lists.postgresql.org; Mon, 25 Mar 2019 22:52:10 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=anastigmatix.net; s=default; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:MIME-Version:Date:Message-ID:From:Cc:References:To:Subject:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=Fu4MB0hMwUPiqrm7l303YTXmBupOVnxaWnJzv6Q+tDw=; b=eitEqzm4+z4vz77IXHhObjyjeU d0df96no56RbLIrwfqg1cbx+E6HOIPxn8UODrlZ286cjZYU4chAasGxXbOa1hGjQWivxH5PlCykfm gdH72Hi/jxupdf9eavdSNsHb7CpEfUEKt8DAd/tro/4I7I7QvD2TogV/6ZI1e+rJUgpwl6YhUCBC1 JmAYfmaYTCgiPd7EYTNniiKSUq1+K2Hc9ocC/fMj/UJbh1bQcoZ4ZK5mZknBZUz3j5UNH1xSttyzo K/XT/1FcDg7403byaxLJzcSiS2esNzWxnv2O1x/ljq4qsxsEjhrV3M8LdcSNJ/ezdXFDz+4s/OuYZ 34ArLF3g==; Received: from [184.19.63.78] (port=51409) by bay.acenet.us with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91) (envelope-from ) id 1h8YRr-00GaOW-L2; Mon, 25 Mar 2019 18:52:08 -0400 Subject: Re: Fix XML handling with DOCTYPE To: Ryan Lambert , pgsql-hackers@lists.postgresql.org References: <155355138978.16482.2985962575775445194.pgcf@coridan.postgresql.org> Cc: Pavel Stehule From: Chapman Flack X-Enigmail-Draft-Status: N1110 Message-ID: <5C995B96.6050204@anastigmatix.net> Date: Mon, 25 Mar 2019 18:52:06 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0 MIME-Version: 1.0 In-Reply-To: <155355138978.16482.2985962575775445194.pgcf@coridan.postgresql.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-OutGoing-Spam-Status: No, score=-95.0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - bay.acenet.us X-AntiAbuse: Original Domain - lists.postgresql.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - anastigmatix.net X-Get-Message-Sender-Via: bay.acenet.us: authenticated_id: chap@anastigmatix.net X-Authenticated-Sender: bay.acenet.us: chap@anastigmatix.net X-Source: X-Source-Args: X-Source-Dir: X-From-Rewrite: unmodified, already matched List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 03/25/19 18:03, Ryan Lambert wrote: > The following review has been posted through the commitfest application: > make installcheck-world: tested, passed > Implements feature: tested, passed > Spec compliant: not tested > Documentation: not tested Hi, Thanks for the review! Yes, that part of this commitfest entry has been committed already and will appear in the next minor releases of those branches. That leaves only one patch in this commitfest entry that is still in need of review, namely the update to the documentation. If you happened to feel moved to look over a documentation patch, that would be what this CF entry most needs in the waning days of the commitfest. There seem to be community members reluctant to review it because of not feeling sufficiently expert in XML to scrutinize every technical detail, but there are other valuable angles for documentation review. (And the reason there *is* a documentation patch is the plentiful room for improvement in the documentation that's already there, so as far as reviewing goes, the old yarn about the two guys, the running shoes, and the bear comes to mind.) I can supply pointers to specs, etc., for anyone who does see some technical details in the patch and has questions about them. Regards, -Chap