- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 2,254 for THE (0.15 sec)
-
CREDITS
APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Fri Apr 26 06:31:35 GMT 2024 - 1.6M bytes - Viewed (0) -
apache-maven/src/main/appended-resources/licenses/EPL-1.0.txt
Agreement. The Eclipse Foundation is the initial Agreement Steward. The Eclipse Foundation may assign the responsibility to serve as the Agreement Steward to a suitable separate entity. Each new version of the Agreement will be given a distinguishing version number. The Program (including Contributions) may always be distributed subject to the version of the Agreement under which it was received. In addition, after a new version of the Agreement is published,
Plain Text - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Mon Sep 17 05:50:12 GMT 2018 - 11.1K bytes - Viewed (0) -
licenses/sigs.k8s.io/json/LICENSE
APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "{}" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed Jan 05 01:31:25 GMT 2022 - 12.6K bytes - Viewed (0) -
architecture/build-state-model.md
"Build tree" is another name for the build definition. The "build tree state" holds the state for the entire build definition for a single build execution within a session. The build tree state is managed by the `BuildTreeState` class. An instance is created at the start of a build execution and discarded at the end of the execution. ### Build state
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Sun May 05 22:45:11 GMT 2024 - 3.4K bytes - Viewed (0) -
LICENSES/vendor/go.opencensus.io/LICENSE
APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a
Plain Text - Registered: Fri Apr 05 09:05:09 GMT 2024 - Last Modified: Wed Jul 01 20:12:36 GMT 2020 - 11.2K bytes - Viewed (0) -
LICENSE
APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a
Plain Text - Registered: Fri May 03 12:43:13 GMT 2024 - Last Modified: Wed Feb 22 18:59:39 GMT 2023 - 11.1K bytes - Viewed (0) -
LICENSE
APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a
Plain Text - Registered: Wed May 08 00:11:12 GMT 2024 - Last Modified: Thu Feb 20 19:53:57 GMT 2020 - 11.1K bytes - Viewed (0) -
licenses/cloud.google.com/go/logging/LICENSE
APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Feb 23 21:41:04 GMT 2021 - 11.1K bytes - Viewed (0) -
licenses/cel.dev/expr/LICENSE
APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Apr 08 17:05:56 GMT 2024 - 11.1K bytes - Viewed (0) -
licenses/github.com/envoyproxy/protoc-gen-validate/LICENSE
APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Sat Oct 26 02:47:39 GMT 2019 - 11.1K bytes - Viewed (0)