Reference in New Issue
Block a user
Delete Branch "refactor/links"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Replaces obsolete links to the retired SVN / WebSVN infrastructure with their current Gitea equivalents across the repo, and refreshes the bundled application table.
Changes:
data/common/templates/table_apps(rus).csv- WebSVN URLs → Gitea; dropped the dead /trunk path segment (flattened during the Git migration); unified the whole file to http:// (it is opened from within KolibriOS, whose network stack has no HTTPS); normalized forum/wiki columns and updated several app entries (descriptions, moved paths, new charsets).kernel/**/asmxygen.py- link_root now points to Gitea instead of WebSVN.svn://kolibrios.org/…andsvn:\…pseudo-paths to Gitea URLs ingif.asm,tinypad.asm,amon/gmonreadmes, and ktcchttp.h/conio.h.flappybird/README.md,ha/ReadMe.txt- WebSVN → Gitea.Out of scope:
$Revision$/$Id$, ~1000 files) andkolibri-n.orglinks — left for separate PRs.flappybird was renamed to floppybird, link https://git.kolibrios.org/KolibriOS/kolibrios/src/branch/main/programs/games/flappybird not work
@Sweetbread - still in progress?
I suppose, there are no more mention of websvn.kolibrios.org in repository.
Would be grateful, if anyone can double-check this.
WIP: refactor/linksto refactor/links: update obsolote WebSVN links (fix #66, #67, ref #77)cc4b210ac5todfd89a5bd2All links are HTTPS, but in data/common/templates/table_apps(rus).csv are HTTP. @Burer, are you sure?
As far as I understand, this file was created as demostration of
tableapp, so it is intended to be opened inside KOS, where HTTPS doesn't make much sence.Looking over, the
httplinks are preferable to access easily using KolibriOS... but they don't work or are auto-routed to the securehttpspage. So suggest changing tohttpsuniversally.Edit: Reading latest comments- has this been tested and works inside KOS?
Well, it seems to work fine for me, as shown in attached image.
And, once again, in my understanding this was intended as KOS-inside file, so no reason for HTTPS here.
But I may be wrong.