Re: New developer papercut - Makefile references INSTALL
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Magnus Hagander <magnus@hagander.net>
Cc: Andres Freund <andres@anarazel.de>, Robert Haas <robertmhaas@gmail.com>, 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-07T22:51:11Z
Lists: pgsql-hackers
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". > If not, could we make the change of URL a part of the branching step? > Branch to a stable release would the include modifying README, and be > mad ea step of version_stamp.pl? Doesn't really help people working from git, I think, because the master branch is always going to claim to be "devel" even when you rewind it to some old state. Maybe we can assume people doing such a thing have even more clue ... but on the whole I'd rather not add the additional complication. regards, tom lane
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Dynamically find correct installation docs in Makefile.
- c330b75d9cce 15.0 landed