Gabriel Scherer

I don't understand what you want. Could you clarify?

Well `include` does not affect `ocamldep` directly (there is nothing related to the include paths in the ocamldep calls), but rather which modules are known to exist when compiling other...

It would certainly be nice, but I haven't been able to do it yet. If someone was willing to lend a hand by looking at the Changelog and marking new...

Actually grepping through the ocaml.org sources, it looks like a "latest" schema is already supported https://github.com/ocaml/ocaml.org/blob/0b9086770d29b45fc8a1dc69dcc580330ba83ecd/src/ocamlorg_frontend/url.ml#L22-L26 (but weirdly enough the "latest" and "with_version" URLs have different structure) The problem is...

> After all these years of efforts on the ocaml website that's something simple and obvious we could expect. Aha, years of effort on the compilers as well and many...

All your proposals are definitive improvements, and I'm in favor of any. (Any opinion on what the gray "version 4.14" link in the top left corner should point to?) @sabine...

Sure, and I think "a select element on the page" is possibly the right thing to replace the current "version 4.14" link that goes to a probably-not-what-you-were-hoping place. But the...

> ETA2: we won't have to consider a "stable" version, right? Like... latest will always be the latest stable version, and if we have unstable versions, they should be reachable...

So if I understand correctly, "copy link to this version" is intended to fix the issue that, with your proposed URL rewriting scheme, it is not easy to get hold...

@dbuenzli when you are on manual/5.0.0, the "latest" link goes to manual/latest, which is a different URL. When you are on manual/latest, "permalink" goes to manual/5.0.0. I don't have a...