Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 175 for Descriptions (0.2 sec)

  1. licenses/github.com/hashicorp/go-version/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 01 22:53:12 GMT 2024
    - Last Modified: Sat Oct 26 02:47:39 GMT 2019
    - 15.6K bytes
    - Viewed (0)
  2. licenses/github.com/pires/go-proxyproto/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 2016 Paulo Pires
    
    Plain Text
    - Registered: Wed Apr 24 22:53:08 GMT 2024
    - Last Modified: Tue Jan 31 17:42:23 GMT 2023
    - 11.1K bytes
    - Viewed (0)
  3. licenses/go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc/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 Apr 24 22:53:08 GMT 2024
    - Last Modified: Wed Jul 26 01:07:39 GMT 2023
    - 11.1K bytes
    - Viewed (0)
  4. licenses/gopkg.in/ini.v1/LICENSE

    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 identification within
    third-party archives.
    
       Copyright 2014 Unknwon
    
    Plain Text
    - Registered: Wed Apr 24 22:53:08 GMT 2024
    - Last Modified: Wed Jan 12 20:05:04 GMT 2022
    - 10K bytes
    - Viewed (0)
  5. licenses/k8s.io/apiserver/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 Apr 24 22:53:08 GMT 2024
    - Last Modified: Wed May 18 01:54:41 GMT 2022
    - 11.1K bytes
    - Viewed (0)
  6. licenses/k8s.io/cli-runtime/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 Apr 24 22:53:08 GMT 2024
    - Last Modified: Sat Oct 26 02:47:39 GMT 2019
    - 11.1K bytes
    - Viewed (0)
  7. licenses/k8s.io/apiextensions-apiserver/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 Apr 24 22:53:08 GMT 2024
    - Last Modified: Sat Oct 26 02:47:39 GMT 2019
    - 11.1K bytes
    - Viewed (0)
  8. licenses/cel.dev/expr/proto/test/v1/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 01 22:53:12 GMT 2024
    - Last Modified: Mon Apr 08 17:05:56 GMT 2024
    - 11.1K bytes
    - Viewed (0)
  9. licenses/cloud.google.com/go/auth/oauth2adapt/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 01 22:53:12 GMT 2024
    - Last Modified: Tue Apr 30 13:56:46 GMT 2024
    - 11.1K bytes
    - Viewed (0)
  10. licenses/github.com/go-jose/go-jose/v4/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 01 22:53:12 GMT 2024
    - Last Modified: Mon Apr 08 17:05:56 GMT 2024
    - 11.1K bytes
    - Viewed (0)
Back to top