Search Options

Results per page
Sort
Preferred Languages
Advance

Results 21 - 30 of 68 for encloses (0.15 sec)

  1. LICENSES/vendor/github.com/pquerna/cachecontrol/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: Fri Apr 26 09:05:10 GMT 2024
    - Last Modified: Fri May 08 04:49:00 GMT 2020
    - 11.2K bytes
    - Viewed (0)
  2. LICENSES/vendor/github.com/prometheus/client_model/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: Fri Apr 26 09:05:10 GMT 2024
    - Last Modified: Fri May 08 04:49:00 GMT 2020
    - 11.2K bytes
    - Viewed (0)
  3. LICENSES/vendor/github.com/prometheus/procfs/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: Fri Apr 26 09:05:10 GMT 2024
    - Last Modified: Fri May 08 04:49:00 GMT 2020
    - 11.2K bytes
    - Viewed (0)
  4. LICENSES/vendor/github.com/moby/spdystream/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: Fri Apr 26 09:05:10 GMT 2024
    - Last Modified: Fri Jan 29 09:26:05 GMT 2021
    - 11.2K bytes
    - Viewed (0)
  5. LICENSES/vendor/github.com/google/gofuzz/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: Fri Apr 26 09:05:10 GMT 2024
    - Last Modified: Fri May 08 04:49:00 GMT 2020
    - 11.2K bytes
    - Viewed (0)
  6. CHANGELOG/CHANGELOG-1.8.md

    SubjectAccessReview API in the `authorization.k8s.io` API group now allows providing the user uid. ([#49677](https://github.com/kubernetes/kubernetes/pull/49677), [@dims](https://github.com/dims))
    
    * After a kubelet rotates its client cert, it now closes its connections to the API server to force a handshake using the new cert. Previously, the kubelet could keep its existing connection open, even if the cert used for that connection was expired and rejected by the API server. ([#49899](https://gi...
    Plain Text
    - Registered: Fri May 03 09:05:14 GMT 2024
    - Last Modified: Tue Feb 20 15:45:02 GMT 2024
    - 312.2K bytes
    - Viewed (1)
  7. LICENSES/third_party/forked/gotestsum/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: Fri May 03 09:05:14 GMT 2024
    - Last Modified: Fri Apr 01 18:49:15 GMT 2022
    - 11.1K bytes
    - Viewed (0)
  8. LICENSES/vendor/go.etcd.io/etcd/pkg/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: Fri Apr 05 09:05:09 GMT 2024
    - Last Modified: Tue Jun 15 14:06:09 GMT 2021
    - 11.2K bytes
    - Viewed (0)
  9. LICENSES/vendor/github.com/google/s2a-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: Fri Apr 26 09:05:10 GMT 2024
    - Last Modified: Wed Oct 25 20:31:21 GMT 2023
    - 11.2K bytes
    - Viewed (0)
  10. LICENSES/vendor/github.com/opencontainers/selinux/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: Fri Apr 26 09:05:10 GMT 2024
    - Last Modified: Fri May 08 04:49:00 GMT 2020
    - 11.2K bytes
    - Viewed (0)
Back to top