написане Tue, 05 Apr 2016 09:45:53 +0300, Ben Cooksley <[email protected]>:
On Mon, Apr 4, 2016 at 8:32 PM, Luigi Toscano <[email protected]>
wrote:
Il 04 aprile 2016 10:11:39 CEST, Ben Cooksley <[email protected]> ha
scritto:
On Sun, Apr 3, 2016 at 10:37 PM, Luigi Toscano
<[email protected]> wrote:
Yuri Chornoivan ha scritto:
написане Sun, 03 Apr 2016 13:19:35 +0300, Luigi Toscano
<[email protected]>:
My understanding is that quickgit.kde.org will be replaced again by
phabricator browser, so we will have to do this again. Moreover,
the old URL
is a proper redirect now.
Hi,
Regretfully, this works for the main page only. Links to the files
are broken.
Example (Okteta):
https://projects.kde.org/projects/kde/kdesdk/okteta/repository/revisions/master/show/kasten/controllers/view/structures/examples/okteta/structures
It is good to wait for the new Phabricator, but I prefer the correct
links
now. And yes, I can do it again (change the links) as soon as the
problems
with Phabricator browser (?) will be resolved.
I didn't mean that we need to wait for the new Phabricator. Given
that the
changes are going into master only anyway, we could wait a bit (which
could be
something like from few hours to few days) to collect the
requirements (like
the one above) and see if it is possible to have an URL which will
redirect to
the proper place, so quickgit for now and Phabricator later, like
commits.kde.org does.
If we don't even ask or discuss, it won't never happen.
I'll wait for the list of requirements to be gathered...
In any event, commits.kde.org/<repository name> is a valid redirect
url for the repository browser for a given repository.
No idea what we would do for file/directory browsing URLs, as commits
was intended for commits.kde.org/repo/commitHash...
I was using commits.kde.org as an example of immutable address survived
and will survive various transitions of the underlying webapp.
So the question is: would you (sysadmin) provide an reliable URL (which
could be still the old projects.kde.org) to access a repository and a
path insidie a repository, useful now for quickgit and later for
Diffusion?
For repository, and branch I see no issue.
I'd like to see the use case of file paths though as i'm not sure how
much they're needed.
Hi,
Developers may refer to files or directories in the source tree for the
materials that are not parts of distribution packages.
Examples:
1. KGeography has scripts to create maps in the source tree:
https://docs.kde.org/trunk5/en/kdeedu/kgeography/how-to-maps.html
2. Krusader has instructions on how to compile it (INSTALL file):
https://docs.kde.org/trunk5/en/extragear-utils/krusader/compilation.html
3. Okteta has examples of structures in the source tree (see "Further
information" section at the bottom):
https://docs.kde.org/trunk5/en/kdesdk/okteta/tools-structures.html#idp60879664
I'm not saying that storing such information directly in the sources is an
ideal solution, but it worked by now.
Hope this helps.
Best regards,
Yuri
Ciao
--
Luigi
Thanks,
Ben
_______________________________________________
kde-doc-english mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kde-doc-english
_______________________________________________
kde-doc-english mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kde-doc-english
