Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 196 for information (0.19 sec)

  1. LICENSES/third_party/forked/shell2junit/LICENSE

               Shell2Junit License Information
    
    Feb, 2010
    
    shell2junit library and sample code is licensed under Apache License, v.2.0.
    
    (c) 2009 Manolo Carrasco (Manuel Carrasco MoƱino)
    
    =====
    
    Apache License
    Version 2.0, January 2004
    http://www.apache.org/licenses/ 
    
    1. Definitions.
    
    "License" shall mean the terms and conditions for use, reproduction, and 
    distribution as defined by Sections 1 through 9 of this document. 
    
    Plain Text
    - Registered: Fri Apr 26 09:05:10 GMT 2024
    - Last Modified: Thu Jul 08 11:48:19 GMT 2021
    - 9.2K bytes
    - Viewed (0)
  2. licenses/github.com/cncf/udpa/go/LICENSE

          To apply the Apache License to your work, attach the following
          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
    Plain Text
    - Registered: Wed Apr 03 22:53:10 GMT 2024
    - Last Modified: Wed Nov 27 21:50:41 GMT 2019
    - 11.1K bytes
    - Viewed (0)
  3. licenses/gomodules.xyz/jsonpatch/v2/LICENSE

          To apply the Apache License to your work, attach the following
          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
    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)
  4. licenses/google.golang.org/genproto/googleapis/api/LICENSE

          To apply the Apache License to your work, attach the following
          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
    Plain Text
    - Registered: Wed Apr 24 22:53:08 GMT 2024
    - Last Modified: Thu Jun 01 21:17:01 GMT 2023
    - 11.1K bytes
    - Viewed (0)
  5. licenses/istio.io/api/LICENSE

          To apply the Apache License to your work, attach the following
          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
    Plain Text
    - Registered: Wed Apr 24 22:53:08 GMT 2024
    - Last Modified: Tue Oct 31 18:53:28 GMT 2023
    - 11.1K bytes
    - Viewed (0)
  6. licenses/istio.io/client-go/LICENSE

          To apply the Apache License to your work, attach the following
          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
    Plain Text
    - Registered: Wed Apr 24 22:53:08 GMT 2024
    - Last Modified: Tue Oct 31 18:53:28 GMT 2023
    - 11.1K bytes
    - Viewed (0)
  7. licenses/helm.sh/helm/v3/LICENSE

          To apply the Apache License to your work, attach the following
          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
    Plain Text
    - Registered: Wed Apr 24 22:53:08 GMT 2024
    - Last Modified: Thu Apr 23 04:14:15 GMT 2020
    - 11.1K bytes
    - Viewed (0)
  8. licenses/go.opentelemetry.io/otel/sdk/metric/LICENSE

          To apply the Apache License to your work, attach the following
          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
    Plain Text
    - Registered: Wed Apr 24 22:53:08 GMT 2024
    - Last Modified: Mon Jul 17 20:25:52 GMT 2023
    - 11.1K bytes
    - Viewed (0)
  9. licenses/google.golang.org/grpc/LICENSE

          To apply the Apache License to your work, attach the following
          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
    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)
  10. licenses/k8s.io/utils/LICENSE

          To apply the Apache License to your work, attach the following
          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
    Plain Text
    - Registered: Wed Apr 24 22:53:08 GMT 2024
    - Last Modified: Mon Oct 28 19:33:59 GMT 2019
    - 11.1K bytes
    - Viewed (0)
Back to top