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 1izu4J-0002nC-RW for pgsql-hackers@arkaria.postgresql.org; Fri, 07 Feb 2020 03:12:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1izu4I-0000su-KJ for pgsql-hackers@arkaria.postgresql.org; Fri, 07 Feb 2020 03:12:34 +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 1izu4I-0000sm-30 for pgsql-hackers@lists.postgresql.org; Fri, 07 Feb 2020 03:12:34 +0000 Received: from mail-yb1-f177.google.com ([209.85.219.177]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1izu4E-0001oE-CD for pgsql-hackers@postgresql.org; Fri, 07 Feb 2020 03:12:32 +0000 Received: by mail-yb1-f177.google.com with SMTP id v12so189849ybi.5 for ; Thu, 06 Feb 2020 19:12:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=JNCF6qZA7Tp6VgvuTlrNqQJdTgPyb+/cYCGlbBy95ss=; b=mSXemCII1anoldpMwTjxr5Kqpk6INoQ3t+OVJIBM2MpIC0Rv4rQM43PB6XcrRl1GHS XOov5MIPtHQ5Fi3bWdlDtwpr/s3nOLZSWpZVyJl9SppaaxBns+RnEnjLnE5wrnURK1HW T926kLly9jKrwBFInvsn82/7ywVQZiNTnEXXnUlORCQM4XQ02V0kmfW92r52O/zHnbs7 3b8ZwOQdMI6xL53R8ToGtMxcT6L5UqB62oWPpcD1DyDCwuxW8HgXVobeVWL7MBcN5w9s 7A+5fbyjk8p0oX3sIzjIYc8HUr09e9FHYO6XnL+kAJow5oVz7+e4fDW3zHIhoe9vMKQ1 AP7w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=JNCF6qZA7Tp6VgvuTlrNqQJdTgPyb+/cYCGlbBy95ss=; b=WZy9QKPU3NQOZ0PWp/5VAPFNWKNxox3NX508sdQTm7kbRUCfL3SN1wEbDsy7pQOza3 5KTnfCXfYwQcTMtlrRGG0qPqDQ0tOqZ5J8ABG2Ztvv+3w3kMbBh7EyVOyoNRdMdeTlVC Oe59WPhrcOnEY2RFaZ9RrDSYjGu/jhYxXYhG7jS/TGTyijTv6l9QdnrOwkqor+Wd8G6J Oq5xcvmgocX/f1Og+80u2lh91SAawL024UWPb5iQ/BXVPP9QYAuPXe+qjvv9k1Zgf9fj ZhPBMZRzcdeTXIX3UbAUS9WXZOIz+Zar8XEefyTJdvb/jR79vn6bvP28hwtuC4r5P7Df oJwQ== X-Gm-Message-State: APjAAAXTbVqCvnB1Q+NThqXV7yGpJ/ysBMmnEVNAsaN5QivS9aQcRuli hPvc7pHl3LXHYbykwk5XOpbxeg== X-Google-Smtp-Source: APXvYqx14FbGC1tXuxHdEHalGJcNfDAACC4K2qo6zCqW66oNPSf6qXQoXzp1ddAspM4ZwKfZB1FIFw== X-Received: by 2002:a25:5945:: with SMTP id n66mr6548451ybb.337.1581045089395; Thu, 06 Feb 2020 19:11:29 -0800 (PST) Received: from pryzbyj (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id o4sm739374ywd.5.2020.02.06.19.11.28 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 06 Feb 2020 19:11:28 -0800 (PST) Received: by pryzbyj (Postfix, from userid 1000) id 648D38007F7; Thu, 6 Feb 2020 21:11:26 -0600 (CST) Date: Thu, 6 Feb 2020 21:11:26 -0600 From: Justin Pryzby To: Amit Kapila Cc: Michael Paquier , pgsql-hackers@postgresql.org Subject: Re: typos in comments and user docs Message-ID: <20200207031126.GN403@telsasoft.com> References: <20200206021432.GA24549@telsasoft.com> <20200206051502.GG23913@paquier.xyz> <20200206135640.GG403@telsasoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Fri, Feb 07, 2020 at 08:33:40AM +0530, Amit Kapila wrote: > On Thu, Feb 6, 2020 at 7:26 PM Justin Pryzby wrote: > > > > On Thu, Feb 06, 2020 at 04:43:18PM +0530, Amit Kapila wrote: > > > On Thu, Feb 6, 2020 at 10:45 AM Michael Paquier wrote: > > > > > > > > On Thu, Feb 06, 2020 at 08:47:14AM +0530, Amit Kapila wrote: > > > > > Your changes look fine to me on the first read. I will push this to > > > > > HEAD unless there are any objections. If we want them in > > > > > back-branches, we might want to probably segregate the changes based > > > > > on the branch until those apply. > > > > > > > > +1. It would be nice to back-patch the user-visible changes in the > > > > docs. > > > > > > > > > > Fair enough, Justin, is it possible for you to segregate the changes > > > that can be backpatched? > > > > Looks like the whole patch can be applied to master and v12 [0]. > > If we decide to backpatch, then why not try to backpatch as far as > possible (till 9.5)? If so, then it would be better to separate > changes which can be backpatched till 9.5, if that is tedious, then > maybe we can just back-patch (in 12) bloom.sgml change as a separate > commit and rest commit it in HEAD only. What do you think? I don't think I was clear. My original doc review patches were limited to this: On Sat, Mar 30, 2019 at 05:43:33PM -0500, Justin Pryzby wrote: > I reviewed docs like this: > git log -p remotes/origin/REL_11_STABLE..HEAD -- doc STABLE..REL_12_STABLE. So after a few minutes earlier today of cherry-pick, I concluded that only bloom.sgml is applicable further back than v12. Probably, I either noticed that minor issue at the same time as nearby doc changes in v12(?), or maybe noticed that issue later, independently of doc review, but then tacked it on to the previous commit, for lack of any better place. Justin