- Sort Score
- Result 10 results
- Languages All
Results 231 - 240 of 352 for _comment (0.05 sec)
-
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
Registered: Wed Oct 30 22:53:10 UTC 2024 - Last Modified: Fri Jul 30 04:02:55 UTC 2021 - 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
Registered: Wed Oct 30 22:53:10 UTC 2024 - Last Modified: Sat Oct 26 02:47:39 UTC 2019 - 11.1K bytes - Viewed (0) -
licenses/github.com/howardjohn/unshare-go/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
Registered: Wed Oct 30 22:53:10 UTC 2024 - Last Modified: Wed Jan 31 07:51:36 UTC 2024 - 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
Registered: Wed Oct 30 22:53:10 UTC 2024 - Last Modified: Mon Apr 11 20:58:15 UTC 2022 - 11.1K bytes - Viewed (0) -
licenses/github.com/moby/spdystream/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
Registered: Wed Oct 30 22:53:10 UTC 2024 - Last Modified: Thu Apr 22 22:59:25 UTC 2021 - 11.1K bytes - Viewed (0) -
licenses/github.com/prometheus/client_model/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
Registered: Wed Oct 30 22:53:10 UTC 2024 - Last Modified: Mon Oct 28 19:33:59 UTC 2019 - 11.1K bytes - Viewed (0) -
licenses/go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp/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
Registered: Wed Oct 30 22:53:10 UTC 2024 - Last Modified: Thu Jun 27 20:56:17 UTC 2024 - 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
Registered: Wed Oct 30 22:53:10 UTC 2024 - Last Modified: Mon Jul 17 20:25:52 UTC 2023 - 11.1K bytes - Viewed (0) -
licenses/google.golang.org/genproto/googleapis/rpc/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
Registered: Wed Oct 30 22:53:10 UTC 2024 - Last Modified: Thu Jun 01 21:17:01 UTC 2023 - 11.1K bytes - Viewed (0) -
licenses/istio.io/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
Registered: Wed Oct 30 22:53:10 UTC 2024 - Last Modified: Tue Oct 31 18:53:28 UTC 2023 - 11.1K bytes - Viewed (0)