Am Samstag, 21. Mai 2016, 13:29:36 CEST schrieb Ben Cooksley: > Hi all, > > The following has now been setup: > > commits.kde.org/<repo>/<commit> -> view for that commit > commits.kde.org/<repo> -> view for that repository > > In addition, the following parameters are supported: > - branch: fairly self explanatory > - path: to a file. If you wish to pass a directory, make sure it has a > trailing slash. > > Examples: > > https://commits.kde.org/repo-management/2cce855af48ec3d3ffaf295f27d66212f2d1 > 8f6e https://commits.kde.org/repo-management > https://commits.kde.org/okular?branch=Applications/16.04 > https://commits.kde.org/okular?path=CMakeLists.txt > https://commits.kde.org/okular?path=cmake/ > https://commits.kde.org/okular?branch=Applications/16.04&path=CMakeLists.txt > https://commits.kde.org/okular?branch=Applications/16.04&path=cmake/ > > Note that where branch is not present, the determination of what > branch to display from will be made by GitPHP / Quickgit, but will > probably be the default branch 'master'. > > Where a branch alone is specified (no path) then Quickgit will display > a listing of recent changes to that branch. > A plain request will continue to direct users to the overview page for > a repository. > Thanks a lot Ben.
I have added this infos to https://techbase.kde.org/Projects/Documentation/KDE_(health_table) Should we use an entity like <!ENTITY kderepo "&https://commits.kde.org;";>? -- Burkhard Lück _______________________________________________ kde-doc-english mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-doc-english
