public inbox for [email protected]  

help / color / mirror / Atom feed

From: Bruce Momjian <[email protected]>
To: Simon Riggs <[email protected]>
Cc: Ian Barwick <[email protected]>
Cc: R Ransbottom <[email protected]>
Cc: Stephen Frost <[email protected]>
Cc: Laurenz Albe <[email protected]>
Cc: [email protected]
Subject: Re: Documentation: 21.5. Default Roles
Date: Mon, 20 Jan 2020 17:13:57 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <CANP8+jJ7OcuGTgvk+S-fvWSj_KPjemV6vvhamj1g9zHuQx7a2A@mail.gmail.com>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<CANP8+jJ7OcuGTgvk+S-fvWSj_KPjemV6vvhamj1g9zHuQx7a2A@mail.gmail.com>

On Mon, Jan 20, 2020 at 06:45:16PM +0000, Simon Riggs wrote:
> On Mon, 20 Jan 2020 at 16:03, Bruce Momjian <[email protected]> wrote:
>     Usually when I apply "wording" doc patches to head only, someone
>     complains that it should be backpatched, so I did that in this case.  If
>     we want to change that idea, we need to agree on the criteria.
> 
> True, but it's not a wording patch, you're entirely renaming a feature.
> 
> I agree with the change of default to predefined, but it shouldn't be
> backpatched.
> 
> There should be a comment in there that it was previously known as "default
> roles", with indexed terms for both.

Well, I am renaming the documentation label for the feature.  Is that
different than wording?  I guess I can see that.  If everyone agrees I
can revert the backpatch, but I don't want to do that if other people
are going to say this should be backpatched.

-- 
  Bruce Momjian  <[email protected]>        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 +

view thread (45+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Documentation: 21.5. Default Roles
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox