Re: New developer papercut - Makefile references INSTALL
От | Tom Lane |
---|---|
Тема | Re: New developer papercut - Makefile references INSTALL |
Дата | |
Msg-id | 273569.1646693471@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: New developer papercut - Makefile references INSTALL (Magnus Hagander <magnus@hagander.net>) |
Ответы |
Re: New developer papercut - Makefile references INSTALL
Re: New developer papercut - Makefile references INSTALL |
Список | 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
В списке pgsql-hackers по дате отправления: