Re: documentation structure

From: Tatsuo Ishii <ishii(at)postgresql(dot)org>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: david(dot)g(dot)johnston(at)gmail(dot)com, andrew(at)dunslane(dot)net, corey(dot)huinker(at)gmail(dot)com, jian(dot)universality(at)gmail(dot)com, robertmhaas(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: documentation structure
Date: 2024-07-20 00:47:17
Message-ID: 20240720.094717.1695122772235543142.ishii@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>> IMO the file name should match the ID of the sect1 element with the leading
>> "functions-" removed, naming the directory "functions". Thus when viewing
>> the web page the corresponding sgml file is determinable.
>
> I'd go for shorter myself (ie "func/"), mainly due to the precedent
> of the existing subdirectory which is "ref/" not "reference/".
> It's hardly a big deal though.

I don't have strong preference neither but I agree that "func/" is
more consistent with existing subdirectory names.

Best reagards,
--
Tatsuo Ishii
SRA OSS LLC
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David G. Johnston 2024-07-20 01:00:18 Re: documentation structure
Previous Message Paul George 2024-07-19 23:32:22 Re: behavior of GROUP BY with VOLATILE expressions