- Sort Score
- Result 10 results
- Languages All
Results 21 - 30 of 133 for syntax (0.2 sec)
-
licenses/gopkg.in/yaml.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/go.opencensus.io/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/structured-merge-diff/v4/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: Sun Aug 30 14:15:49 GMT 2020 - 11.1K bytes - Viewed (0) -
licenses/sigs.k8s.io/gateway-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 Feb 19 17:47:08 GMT 2021 - 11.1K bytes - Viewed (0) -
licenses/github.com/census-instrumentation/opencensus-proto/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/containernetworking/cni/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/monitoring/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/google/gofuzz/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/kylelemons/godebug/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/go.opentelemetry.io/otel/metric/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 17 20:25:52 GMT 2023 - 11.1K bytes - Viewed (0)