Re: New developer papercut - Makefile references INSTALL

Robert Haas <robertmhaas@gmail.com>

From: Robert Haas <robertmhaas@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Magnus Hagander <magnus@hagander.net>, Andres Freund <andres@anarazel.de>, Josef Šimánek <josef.simanek@gmail.com>, samay sharma <smilingsamay@gmail.com>, Tim McNamara <tim@mcnamara.nz>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2022-03-08T17:19:34Z
Lists: pgsql-hackers
On Mon, Mar 7, 2022 at 5:51 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Magnus Hagander <magnus@hagander.net> writes:
> > But taking a step back, who is the actual audience for this? Do we
> > *need* a link pointing directly there, or is it enough to just point
> > to "use the docs on the web"? We can't link to the incorrect version,
> > but can we just link to /docs/ and leave it at that?
>
> Well, it's people compiling from source, so I guess we can assume some
> amount of cluefulness?  I think perhaps it'd be okay to say "go here
> and then navigate to the proper sub-page for your version".

It's kind of hard for me to imagine that not being enough for somebody.

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



Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Dynamically find correct installation docs in Makefile.