Re: split func.sgml to separated individual sgml files

From: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
To: jian he <jian(dot)universality(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: split func.sgml to separated individual sgml files
Date: 2024-11-13 20:10:46
Message-ID: CADkLM=eq_aLWJmU2qc7mvS6W0iLqxKbJf8nMFxv-e8msFYpNKw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
> The following is step-by-step logic.
>
>
The end result (one file per section) seems good to me.

I suspect that reviewer burden may be the biggest barrier to going forward.
Perhaps breaking up the changes so that each new sect1 file gets its own
commit, allowing the reviewer to more easily (if not programmatically)
verify that the text that moved out of func.sgml moved into
func-sect-foo.sgml.

Granted, the committer will likely squash all of those commits down into
one big one, but by the the hard work of reviewing is done by then.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dmitry Dolgov 2024-11-13 20:30:23 Re: btree: implement dynamic prefix truncation (was: Improving btree performance through specializing by key shape, take 2)
Previous Message Robert Haas 2024-11-13 20:06:17 Re: Graceful way to handle too many locks