Searched refs:licensing (Results 1 – 25 of 639) sorted by relevance
12345678910>>...26
2 # CONSULT THE OWNERS AND opensource-licensing@google.com BEFORE22 license_note: "explicitly approved by opensource-licensing@ on Feb. 12 2021.\n"
2 # CONSULT THE OWNERS AND opensource-licensing@google.com BEFORE24 " culp/ligatures font with CC-BY-NC-SA licensing. Google does not want to\n"
3 Please see the file LICENCE in the PCRE2 distribution for licensing details.
3 Bazel rules for defining and using package licensing and other metadata
2 # CONSULT THE OWNERS AND opensource-licensing@google.com BEFORE
17 // CONSULT THE OWNERS AND opensource-licensing@google.com BEFORE21 // CONSULT THE OWNERS AND opensource-licensing@google.com BEFORE
45 such code and/or adjust the licensing conditions notice accordingly.50 and/or adjust the licensing conditions notice accordingly.
2 different tools and libraries which each carry their own licensing
19 you should contact the Copyright Holder and seek a different licensing43 licensing fees.105 redistribute the Modified Version using the same licensing terms that apply to131 that you do not charge a licensing fee for the Package. Distributor Fees are132 permitted, and licensing fees for other components in the aggregation are
15 - Removed the bench.sh since the file doesn't have the licensing info and