| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com>, Josef Šimánek <josef(dot)simanek(at)gmail(dot)com>, samay sharma <smilingsamay(at)gmail(dot)com>, Tim McNamara <tim(at)mcnamara(dot)nz>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: New developer papercut - Makefile references INSTALL |
| Date: | 2022-03-07 22:51:11 |
| Message-ID: | 273569.1646693471@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Magnus Hagander <magnus(at)hagander(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zhihong Yu | 2022-03-07 22:53:15 | Re: support for MERGE |
| Previous Message | Melanie Plageman | 2022-03-07 22:09:19 | Re: make tuplestore helper function |