- Sort Score
- Result 10 results
- Languages All
Results 11 - 20 of 101 for syntax (0.13 sec)
-
licenses/gomodules.xyz/jsonpatch/v2/LICENSE
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 file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.
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) -
licenses/istio.io/client-go/LICENSE
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 file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Oct 31 18:53:28 GMT 2023 - 11.1K bytes - Viewed (0) -
licenses/sigs.k8s.io/mcs-api/LICENSE
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 file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Fri Mar 12 21:17:55 GMT 2021 - 11.1K bytes - Viewed (0) -
licenses/k8s.io/utils/LICENSE
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 file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Oct 28 19:33:59 GMT 2019 - 11.1K bytes - Viewed (0) -
licenses/istio.io/api/LICENSE
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 file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Oct 31 18:53:28 GMT 2023 - 11.1K bytes - Viewed (0) -
licenses/github.com/klauspost/compress/LICENSE
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 file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Nov 30 19:13:15 GMT 2021 - 16.3K bytes - Viewed (0) -
licenses/sigs.k8s.io/yaml/LICENSE
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 file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Oct 31 19:53:28 GMT 2023 - 15.8K bytes - Viewed (0) -
LICENSE
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 file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Oct 31 14:48:35 GMT 2023 - 11.1K bytes - Viewed (0) -
licenses/github.com/containernetworking/plugins/LICENSE
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 file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Jun 16 20:42:16 GMT 2020 - 11.1K bytes - Viewed (0) -
licenses/cloud.google.com/go/compute/metadata/LICENSE
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 file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Nov 01 23:31:22 GMT 2022 - 11.1K bytes - Viewed (0)