Thanks for proposal and actually I have had the same idea for a long time that SVN should no longer be used for the OpenCL headers.
However, I prefer to add these headers to third_party/khronos in chromium-crosswalk.git like https://github.com/crosswalk-project/chromium-crosswalk/pull/188, just as how OpenGL headers are managed in Chromium, instead of hosting them in a dedicated repo. WDYT? Best Regards Jiajie -----Original Message----- From: Crosswalk-dev [mailto:[email protected]] On Behalf Of Raphael Kubo da Costa Sent: Wednesday, August 26, 2015 1:33 AM To: [email protected] Subject: [Crosswalk-dev] Intent to switch: using our own GitHub copy of the OpenCL headers This isn't really an intent to implement, but the idea is similar. So far we've been fetching the OpenCL headers we use for WebCL directly from Khronos's SVN repository. We probably rolled to a different revision only once so far. As people who live behind corporate proxies know, SVN is yet another thing that needs to be configured, and access to Khronos's repository can be flaky at times. I would then like to make a copy of the repository and host it in the crosswalk-project organization, with a name like khronos-cl-api-1.2 instead. This allows us to switch back to a workflow entirely based on git, which makes things easier from a maintenance perspective. I have made a test conversion with git-svn and hosted it here: https://github.com/rakuco/khronos-cl-api-1.2 Does anyone have objections? _______________________________________________ Crosswalk-dev mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev _______________________________________________ Crosswalk-dev mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
