- Sort Score
- Result 10 results
- Languages All
Results 11 - 20 of 183 for comment (0.21 sec)
-
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
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) -
licenses/github.com/google/go-containerregistry/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
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Fri Jul 30 04:02:55 GMT 2021 - 11.1K bytes - Viewed (0) -
licenses/github.com/containerd/stargz-snapshotter/estargz/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
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Fri Jul 30 04:02:55 GMT 2021 - 11.1K bytes - Viewed (0) -
licenses/github.com/prometheus/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
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed Jul 14 16:53:19 GMT 2021 - 11.1K bytes - Viewed (0) -
licenses/github.com/moby/buildkit/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
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Apr 11 20:58:15 GMT 2022 - 11.1K bytes - Viewed (0) -
licenses/go.opentelemetry.io/otel/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
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) -
licenses/go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp/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
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed Jul 26 01:07:39 GMT 2023 - 11.1K 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
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/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
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/iam/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
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Dec 12 23:58:49 GMT 2022 - 11.1K bytes - Viewed (0)