- Sort Score
- Result 10 results
- Languages All
Results 1271 - 1280 of 1,429 for Description (0.14 sec)
-
licenses/github.com/google/pprof/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 Mar 21 21:50:09 UTC 2022 - 11.1K bytes - Viewed (0) -
licenses/github.com/grpc-ecosystem/go-grpc-middleware/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/github.com/modern-go/reflect2/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/github.com/prometheus/common/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/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]
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/go.opentelemetry.io/otel/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/exporters/otlp/otlptrace/otlptracehttp/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: Wed Jul 26 01:07:39 UTC 2023 - 11.1K bytes - Viewed (0) -
LICENSES/third_party/forked/gotestsum/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 Apr 01 18:49:15 UTC 2022 - 11.1K 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: Sun Nov 03 03:35:11 UTC 2024 - Last Modified: Wed Sep 11 20:39:30 UTC 2013 - 11.1K bytes - Viewed (0) -
licenses/github.com/google/shlex/COPYING
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 22 22:59:25 UTC 2021 - 11.1K bytes - Viewed (0)