Maybe just use the hub redirection, e.g.
https://hub.libreoffice.org/git-core/40264372657160b69b9639eff4fe0263af8f9033
https://hub.libreoffice.org/git-online/eaa4a7838a913979eddd2304053b1697ad596586
Using the hub has the advantage that the links would still work even if
cgit.fdo was no longer available, or gitiles was gone, or has another
URL syntax, etc.
Regards
Samuel
Am 20.03.2019 um 17:24 schrieb Luke Benes:
Could you please change the Commit Notification bot back to cgit?
In the 6 months, that I have been testing gitiles, I have found no advantages and many
disadvantages over cgit. In general, it presents information in an inferior way and it’s URL’s have
led to multiple copy and paste errors, causing delays in work when the errors were missed.
In his last email, Mike explains how the gitiles timestamps lead to confusion. This is a serious
problem for my use case. The other major problem, are the random symbols like “^!” appended to the
ends of commit IDs in URLs. I’ve been copy and pasting commit IDs from cgit for years and never
once had a problem. With gitiles, it happens regularly despite me being aware.
When I asked for feedback on the IRC dev channel, no one voiced preference for gitiles. I only
heard agreement that the URLs and log format are inferior to cgit's.
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.