- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 173 for Normal (0.4 sec)
-
LICENSE
is widely used among developers working in that language. The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Fri Apr 23 18:58:53 GMT 2021 - 33.7K bytes - Viewed (0) -
LICENSES/vendor/github.com/gogo/protobuf/LICENSE
= vendor/github.com/gogo/protobuf licensed under: = Copyright (c) 2013, The GoGo Authors. All rights reserved. Protocol Buffers for Go with Gadgets Go support for Protocol Buffers - Google's data interchange format Copyright 2010 The Go Authors. All rights reserved. https://github.com/golang/protobuf Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Plain Text - Registered: Fri Apr 26 09:05:10 GMT 2024 - Last Modified: Fri May 08 04:49:00 GMT 2020 - 1.8K bytes - Viewed (0) -
licenses/go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp/LICENSE
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 Apr 24 22:53:08 GMT 2024 - Last Modified: Fri Dec 15 21:30:37 GMT 2023 - 11.1K bytes - Viewed (0) -
licenses/k8s.io/kube-openapi/pkg/validation/errors/LICENSE
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 Apr 24 22:53:08 GMT 2024 - Last Modified: Wed Dec 16 22:26:43 GMT 2020 - 11.1K bytes - Viewed (0) -
licenses/k8s.io/kube-openapi/pkg/validation/strfmt/LICENSE
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 Apr 24 22:53:08 GMT 2024 - Last Modified: Wed Dec 16 22:26:43 GMT 2020 - 11.1K bytes - Viewed (0) -
licenses/k8s.io/kubectl/LICENSE
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 Apr 24 22:53:08 GMT 2024 - Last Modified: Sat Oct 26 02:47:39 GMT 2019 - 11.1K bytes - Viewed (0) -
licenses/go.opentelemetry.io/proto/otlp/LICENSE
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 Apr 24 22:53:08 GMT 2024 - Last Modified: Thu Apr 15 19:34:51 GMT 2021 - 11.1K bytes - Viewed (0) -
licenses/sigs.k8s.io/controller-runtime/LICENSE
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 Apr 24 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/sdk/LICENSE
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 Apr 24 22:53:08 GMT 2024 - Last Modified: Mon Jul 17 20:25:52 GMT 2023 - 11.1K bytes - Viewed (0) -
licenses/google.golang.org/genproto/LICENSE
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 Apr 24 22:53:08 GMT 2024 - Last Modified: Sat Oct 26 02:47:39 GMT 2019 - 11.1K bytes - Viewed (0)