- Sort Score
- Result 10 results
- Languages All
Results 111 - 120 of 350 for syntax (0.05 sec)
-
licenses/go.opentelemetry.io/otel/exporters/prometheus/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.
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Mon Jul 17 20:25:52 UTC 2023 - 11.1K bytes - Viewed (0) -
licenses/go.opentelemetry.io/otel/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.
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Mon Jul 17 20:25:52 UTC 2023 - 11.1K bytes - Viewed (0) -
licenses/go.opentelemetry.io/proto/otlp/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.
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Thu Apr 15 19:34:51 UTC 2021 - 11.1K bytes - Viewed (0) -
licenses/google.golang.org/grpc/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.
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Sat Oct 26 02:47:39 UTC 2019 - 11.1K bytes - Viewed (0) -
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.
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Sat Oct 26 02:47:39 UTC 2019 - 11.1K bytes - Viewed (0) -
licenses/helm.sh/helm/v3/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.
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Thu Apr 23 04:14:15 UTC 2020 - 11.1K bytes - Viewed (0) -
licenses/k8s.io/klog/v2/LICENSE
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.
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Fri Jul 24 20:11:50 UTC 2020 - 10K bytes - Viewed (0) -
licenses/k8s.io/kube-openapi/pkg/validation/strfmt/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.
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Wed Dec 16 22:26:43 UTC 2020 - 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.
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Mon Oct 28 19:33:59 UTC 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.
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Thu Apr 22 22:59:25 UTC 2021 - 11.1K bytes - Viewed (0)