- Sort Score
- Result 10 results
- Languages All
Results 11 - 20 of 169 for hocomment (0.17 sec)
-
licenses/gomodules.xyz/jsonpatch/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
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/istio.io/client-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
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Oct 31 18:53:28 GMT 2023 - 11.1K bytes - Viewed (0) -
licenses/sigs.k8s.io/mcs-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
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Fri Mar 12 21:17:55 GMT 2021 - 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
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Oct 28 19:33:59 GMT 2019 - 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
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Oct 31 18:53:28 GMT 2023 - 11.1K bytes - Viewed (0) -
LICENSES/vendor/go.etcd.io/etcd/client/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
Plain Text - Registered: Fri Apr 05 09:05:09 GMT 2024 - Last Modified: Tue Jun 15 14:06:09 GMT 2021 - 11.2K bytes - Viewed (0) -
LICENSES/vendor/github.com/grpc-ecosystem/go-grpc-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: Fri Apr 26 09:05:10 GMT 2024 - Last Modified: Fri May 08 04:49:00 GMT 2020 - 11.2K bytes - Viewed (0) -
licenses/github.com/klauspost/compress/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 30 19:13:15 GMT 2021 - 16.3K bytes - Viewed (0) -
licenses/sigs.k8s.io/yaml/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 19:53:28 GMT 2023 - 15.8K bytes - Viewed (0) -
LICENSES/vendor/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
Plain Text - Registered: Fri Apr 05 09:05:09 GMT 2024 - Last Modified: Wed Jul 01 20:12:36 GMT 2020 - 11.2K bytes - Viewed (0)