Re: documentation structure

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: documentation structure
Дата
Msg-id CA+TgmobJcFAKtS9frnEHTGyV3L54m8NynfHpwRO5fihSYGsHfg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: documentation structure  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Ответы Re: documentation structure  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
On Wed, Mar 20, 2024 at 5:05 PM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
> I think you can achieve this with a much smaller patch that just changes
> the outer tag in each file so that each file is a <sect1>, then create a
> single file that includes all of these plus an additional outer tag for
> the <chapter> (or maybe just add the <chapter> in postgres.sgml).  This
> has the advantage that each AM continues to be a separate single file,
> and you still have your desired structure.

Right, that could also be done, and not just for 0003. I just wasn't
sure that was the right approach. It would mean that the division of
the SGML into files continues to reflect the original chapter
divisions rather than the current ones forever. In the short run
that's less churn, less back-patching pain, etc.; but in the long term
it means you've got relics of a structure that doesn't exist any more
sticking around forever.

--
Robert Haas
EDB: http://www.enterprisedb.com



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Jacob Champion
Дата:
Сообщение: Re: [PATCH] Exponential backoff for auth_delay
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Patch: Add parse_type Function