Max Marrone via llvm-dev
2019-Jun-10 22:07 UTC
[llvm-dev] What's the relationship between our Phabricator instance and upstream Phabricator?
I was curious about making user experience improvements to our Phabricator instance, but I'm not sure where the code is. https://llvm.org/docs/Phabricator.html#status calls our instance a "derivative of an existing open source project," presumably meaning we're running some kind of fork of the official Phabricator. It links to the GitHub repository https://github.com/r4nt/llvm-reviews/, but that repository hasn't been touched in 5 years. Is that actually what we're deploying? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190610/984f37f2/attachment.html>
Manuel Klimek via llvm-dev
2019-Jun-25 15:21 UTC
[llvm-dev] What's the relationship between our Phabricator instance and upstream Phabricator?
On Tue, Jun 11, 2019 at 12:07 AM Max Marrone <max at marrone.nyc> wrote:> I was curious about making user experience improvements to our Phabricator > instance, but I'm not sure where the code is. > > https://llvm.org/docs/Phabricator.html#status calls our instance a > "derivative of an existing open source project," presumably meaning we're > running some kind of fork of the official Phabricator. It links to the > GitHub repository https://github.com/r4nt/llvm-reviews/, but that > repository hasn't been touched in 5 years. Is that actually what we're > deploying? >That repo just has the equivalent of dockerfiles to set up a machine should the current one die. The deployed repo is https://github.com/r4nt/phabricator/tree/llvm-production -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190625/55f640af/attachment-0001.html>