- Sort Score
- Result 10 results
- Languages All
Results 31 - 40 of 101 for syntax (0.76 sec)
-
licenses/k8s.io/kube-openapi/pkg/validation/errors/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: Wed Dec 16 22:26:43 GMT 2020 - 11.1K bytes - Viewed (0) -
licenses/sigs.k8s.io/controller-runtime/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/sigs.k8s.io/kustomize/kyaml/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: Thu Apr 22 22:59:25 GMT 2021 - 11.1K bytes - Viewed (0) -
licenses/k8s.io/component-base/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/cloud.google.com/go/trace/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) -
licenses/github.com/AdaLogics/go-fuzz-headers/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 Jun 28 18:00:28 GMT 2021 - 11.1K bytes - Viewed (0) -
licenses/cloud.google.com/go/longrunning/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) -
licenses/cloud.google.com/go/auth/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 Apr 30 13:56:46 GMT 2024 - 11.1K bytes - Viewed (0) -
licenses/github.com/google/btree/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/github.com/google/gnostic-models/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 Jul 24 18:16:35 GMT 2023 - 11.1K bytes - Viewed (0)