Jon Leech

I wasn't entirely clear either. A confusing thing I kept running into was how .reuse/dep5 is parsed such that the last match is the controlling one - someone in another...

While there are a couple of different ways of presenting it, for me #3 boils down to * Explicit override of file, when necessary (special case / one-off license /...

It doesn't really matter what the runs on is since everything is packaged in a Docker container running Debian - at present > gcc version 10.2.1 20210110 (Debian 10.2.1-6)

Explicit copyrights could be added to the .adoc files but it's not essential. However, I recommend incorporating REUSE in CI. 'reuse lint' verifies that every file in a repo is...

When resolving conflicts, please note that you will also need to move any changes in this branch to README.md, to corresponding asciidoc markup in README.adoc, and remove README.md .

If you want to propose a PR updating xml/vendors.txt (and maybe renaming it and putting in in .adoc format), that would be fine. There's some historical vendor information in there...

N.b. I think S3 had the most exciting corporate evolution. At one point I needed to track down the current owner of the S3TC IP for legal purposes and it...

Moved to Vulkan-Hpp. Vulkan-Headers is purely a publishing mechanism.

The toolchain is Docbook 4 -> XHTML Transitional. Switching to Docbook 5 -> HTML would be a huge amount of work. I do not know what happens these days if...

All the various versions of GL refpages and the EGL refpages use the same toolchain. I will need to understand exactly what you did aside from file renaming and the...