-
Notifications
You must be signed in to change notification settings - Fork 301
Description
See also cling's web page.
This contains a link with a specific Git commit hash. This commit introduced the wrong link. Following the link, you just find v0.9 from 2021 under "Latest News".
When you replace the commit hash in the link with master (like this), "Latest News" shows the current version also shown under the GitHub releases page. However, the "Read more" links under "Latest News" link to the repo https://github.com/vgvassilev/cling, even though that repo and this one both say in their readme:
The main repository is at https://github.com/root-project/cling
But the "Read more" links under "Latest News" shouldn't just link to the correct repo, but also use links of the style https://github.com/root-project/cling/releases/tag/v1.2 instead of the current https://github.com/root-project/cling/blob/v1.2/docs/ReleaseNotes.md. This release page then has a link to browse the file tree anyways.