Search Options

Results per page
Sort
Preferred Languages
Advance

Results 11 - 20 of 110 for information (0.31 sec)

  1. 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 May 08 22:53:08 GMT 2024
    - Last Modified: Sat Oct 26 02:47:39 GMT 2019
    - 11.1K bytes
    - Viewed (0)
  2. 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 May 08 22:53:08 GMT 2024
    - Last Modified: Tue Oct 31 18:53:28 GMT 2023
    - 11.1K bytes
    - Viewed (0)
  3. licenses/sigs.k8s.io/mcs-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 May 08 22:53:08 GMT 2024
    - Last Modified: Fri Mar 12 21:17:55 GMT 2021
    - 11.1K bytes
    - Viewed (0)
  4. 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 May 08 22:53:08 GMT 2024
    - Last Modified: Mon Oct 28 19:33:59 GMT 2019
    - 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 May 08 22:53:08 GMT 2024
    - Last Modified: Tue Oct 31 18:53:28 GMT 2023
    - 11.1K bytes
    - Viewed (0)
  6. licenses/github.com/klauspost/compress/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 May 08 22:53:08 GMT 2024
    - Last Modified: Tue Nov 30 19:13:15 GMT 2021
    - 16.3K bytes
    - Viewed (0)
  7. licenses/sigs.k8s.io/yaml/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 May 08 22:53:08 GMT 2024
    - Last Modified: Tue Oct 31 19:53:28 GMT 2023
    - 15.8K bytes
    - Viewed (0)
  8. licenses/cloud.google.com/go/trace/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 May 08 22:53:08 GMT 2024
    - Last Modified: Tue Nov 01 23:31:22 GMT 2022
    - 11.1K bytes
    - Viewed (0)
  9. licenses/github.com/AdaLogics/go-fuzz-headers/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 May 08 22:53:08 GMT 2024
    - Last Modified: Mon Jun 28 18:00:28 GMT 2021
    - 11.1K bytes
    - Viewed (0)
  10. licenses/cloud.google.com/go/longrunning/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 May 08 22:53:08 GMT 2024
    - Last Modified: Tue Nov 01 23:31:22 GMT 2022
    - 11.1K bytes
    - Viewed (0)
Back to top