- Sort Score
- Result 10 results
- Languages All
Results 1121 - 1130 of 1,443 for descriptions (0.07 sec)
-
LICENSES/third_party/forked/cgroups/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]
Registered: Fri Nov 01 09:05:11 UTC 2024 - Last Modified: Thu Oct 31 17:42:39 UTC 2024 - 11.1K bytes - Viewed (0) -
LICENSES/vendor/github.com/containerd/ttrpc/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]
Registered: Fri Nov 01 09:05:11 UTC 2024 - Last Modified: Fri May 08 04:49:00 UTC 2020 - 11.2K bytes - Viewed (0) -
LICENSE.txt
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]
Registered: Fri Nov 01 11:42:11 UTC 2024 - Last Modified: Mon Jul 23 14:02:28 UTC 2012 - 11.1K bytes - Viewed (0) -
update-credits.sh
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]
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Fri Aug 11 05:08:38 UTC 2023 - 11.4K 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]
Registered: Wed Nov 06 00:11:12 UTC 2024 - Last Modified: Thu Feb 20 19:53:57 UTC 2020 - 11.1K bytes - Viewed (0) -
licenses/go.opentelemetry.io/otel/exporters/prometheus/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]
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Mon Jul 17 20:25:52 UTC 2023 - 11.1K bytes - Viewed (0) -
licenses/go.opentelemetry.io/otel/trace/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]
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Mon Jul 17 20:25:52 UTC 2023 - 11.1K bytes - Viewed (0) -
licenses/go.opentelemetry.io/proto/otlp/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]
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Thu Apr 15 19:34:51 UTC 2021 - 11.1K bytes - Viewed (0) -
licenses/google.golang.org/grpc/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]
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Sat Oct 26 02:47:39 UTC 2019 - 11.1K bytes - Viewed (0) -
licenses/gopkg.in/yaml.v2/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}
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Sat Oct 26 02:47:39 UTC 2019 - 11.1K bytes - Viewed (0)