| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
| Cc: | tgl(at)sss(dot)pgh(dot)pa(dot)us, 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 01:00:18 |
| Message-ID: | CAKFQuwawj_Ow_a_aD7vfi6hYtnv5+BiQYSKN8cV7ZPo8qNF9xQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jul 19, 2024 at 5:47 PM Tatsuo Ishii <ishii(at)postgresql(dot)org> wrote:
> >> 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.
>
>
Works for me. I was definitely on the fence between the two.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Corey Huinker | 2024-07-20 01:58:33 | Re: Statistics Import and Export |
| Previous Message | Tatsuo Ishii | 2024-07-20 00:47:17 | Re: documentation structure |