pgsql: doc: make ref/*.sgml file header comment layout consistent

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

pgsql: doc: make ref/*.sgml file header comment layout consistent

Bruce Momjian
doc:  make ref/*.sgml file header comment layout consistent

Branch
------
REL_11_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/d9cbdec23fd63a8ac650ab174d5d33ab5fcc3bb4

Modified Files
--------------
doc/src/sgml/ref/checkpoint.sgml           | 5 ++++-
doc/src/sgml/ref/create_cast.sgml          | 5 ++++-
doc/src/sgml/ref/create_collation.sgml     | 5 ++++-
doc/src/sgml/ref/create_conversion.sgml    | 5 ++++-
doc/src/sgml/ref/create_foreign_table.sgml | 5 ++++-
doc/src/sgml/ref/create_function.sgml      | 1 +
doc/src/sgml/ref/create_procedure.sgml     | 1 +
doc/src/sgml/ref/create_transform.sgml     | 5 ++++-
doc/src/sgml/ref/drop_cast.sgml            | 5 ++++-
doc/src/sgml/ref/drop_collation.sgml       | 5 ++++-
doc/src/sgml/ref/drop_conversion.sgml      | 5 ++++-
doc/src/sgml/ref/drop_foreign_table.sgml   | 5 ++++-
doc/src/sgml/ref/drop_transform.sgml       | 5 ++++-
doc/src/sgml/ref/load.sgml                 | 1 +
doc/src/sgml/ref/pg_config-ref.sgml        | 5 ++++-
doc/src/sgml/ref/pg_restore.sgml           | 5 ++++-
doc/src/sgml/ref/pgarchivecleanup.sgml     | 5 ++++-
doc/src/sgml/ref/pgbench.sgml              | 5 ++++-
doc/src/sgml/ref/pgtestfsync.sgml          | 5 ++++-
doc/src/sgml/ref/pgtesttiming.sgml         | 5 ++++-
doc/src/sgml/ref/pgupgrade.sgml            | 5 ++++-
doc/src/sgml/ref/set_constraints.sgml      | 6 +++++-
doc/src/sgml/ref/set_session_auth.sgml     | 6 +++++-
doc/src/sgml/ref/set_transaction.sgml      | 6 +++++-
24 files changed, 90 insertions(+), 21 deletions(-)

Reply | Threaded
Open this post in threaded view
|

Re: pgsql: doc: make ref/*.sgml file header comment layout consistent

Peter Eisentraut-6
On 2020-05-15 14:52, Bruce Momjian wrote:
> doc:  make ref/*.sgml file header comment layout consistent
>
> Branch
> ------
> REL_11_STABLE

Why was this backpatched?

--
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


Reply | Threaded
Open this post in threaded view
|

Re: pgsql: doc: make ref/*.sgml file header comment layout consistent

Bruce Momjian
On Fri, May 22, 2020 at 11:57:39AM +0200, Peter Eisentraut wrote:
> On 2020-05-15 14:52, Bruce Momjian wrote:
> > doc:  make ref/*.sgml file header comment layout consistent
> >
> > Branch
> > ------
> > REL_11_STABLE
>
> Why was this backpatched?

Uh, why not?  There have been requests to keep the docs as consistent as
possible in back branches.

--
  Bruce Momjian  <[hidden email]>        https://momjian.us
  EnterpriseDB                             https://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+                      Ancient Roman grave inscription +


Reply | Threaded
Open this post in threaded view
|

Re: pgsql: doc: make ref/*.sgml file header comment layout consistent

Michael Paquier-2
On Fri, May 22, 2020 at 11:08:45AM -0400, Bruce Momjian wrote:
> On Fri, May 22, 2020 at 11:57:39AM +0200, Peter Eisentraut wrote:
>> Why was this backpatched?
>
> Uh, why not?  There have been requests to keep the docs as consistent as
> possible in back branches.

Because this is a cosmetic-only change and not something user-visible,
so it may be surprising to see it back-patched.  I was a bit surprised
first, but after looking at it I don't have any problem with what you
did, and you actually made the effort to back-patch it.
--
Michael

signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: pgsql: doc: make ref/*.sgml file header comment layout consistent

Bruce Momjian
On Sat, May 23, 2020 at 01:42:38PM +0900, Michael Paquier wrote:

> On Fri, May 22, 2020 at 11:08:45AM -0400, Bruce Momjian wrote:
> > On Fri, May 22, 2020 at 11:57:39AM +0200, Peter Eisentraut wrote:
> >> Why was this backpatched?
> >
> > Uh, why not?  There have been requests to keep the docs as consistent as
> > possible in back branches.
>
> Because this is a cosmetic-only change and not something user-visible,
> so it may be surprising to see it back-patched.  I was a bit surprised
> first, but after looking at it I don't have any problem with what you
> did, and you actually made the effort to back-patch it.

I use doc backpatching logic we discussed in this 2018 thread:

    https://www.postgresql.org/message-id/flat/CABUevEyumGh3r05U3_mhRrEU%3DdfacdRr2HEw140MvN7FSBMSyw%40mail.gmail.com#6a92eb3360700dd4d2d392d2b91021ba

--
  Bruce Momjian  <[hidden email]>        https://momjian.us
  EnterpriseDB                             https://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+                      Ancient Roman grave inscription +