- Sort Score
- Result 10 results
- Languages All
Results 41 - 50 of 175 for Descriptions (0.16 sec)
-
LICENSES/vendor/github.com/prometheus/procfs/LICENSE
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. Copyright [yyyy] [name of copyright owner]
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/vendor/github.com/moby/spdystream/LICENSE
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. Copyright [yyyy] [name of copyright owner]
Plain Text - Registered: Fri Apr 26 09:05:10 GMT 2024 - Last Modified: Fri Jan 29 09:26:05 GMT 2021 - 11.2K bytes - Viewed (0) -
LICENSES/vendor/github.com/google/gofuzz/LICENSE
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. Copyright [yyyy] [name of copyright owner]
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/sigs.k8s.io/json/LICENSE
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. Copyright {yyyy} {name of copyright owner}
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed Jan 05 01:31:25 GMT 2022 - 12.6K bytes - Viewed (0) -
licenses/github.com/hashicorp/errwrap/LICENSE
to the maximum extent possible; and (b) describe the limitations and the code they affect. Such description must be placed in a text file included with all distributions of the Covered Software under this License. Except to the extent prohibited by statute or regulation, such description must be sufficiently detailed for a recipient of ordinary skill to be able to understand it. 5. Termination
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Sat Oct 26 02:47:39 GMT 2019 - 15.6K bytes - Viewed (0) -
licenses/github.com/hashicorp/hcl/LICENSE
to the maximum extent possible; and (b) describe the limitations and the code they affect. Such description must be placed in a text file included with all distributions of the Covered Software under this License. Except to the extent prohibited by statute or regulation, such description must be sufficiently detailed for a recipient of ordinary skill to be able to understand it. 5. Termination
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Sat Oct 26 02:47:39 GMT 2019 - 15.6K bytes - Viewed (0) -
LICENSE
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. Copyright {yyyy} {name of copyright owner}
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/github.com/containernetworking/plugins/LICENSE
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. Copyright {yyyy} {name of copyright owner}
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Jun 16 20:42:16 GMT 2020 - 11.1K bytes - Viewed (0) -
licenses/cloud.google.com/go/compute/metadata/LICENSE
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. Copyright [yyyy] [name of copyright owner]
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
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. Copyright [yyyy] [name of copyright owner]
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)