Search Options

Results per page
Sort
Preferred Languages
Advance

Results 11 - 20 of 68 for encloses (0.17 sec)

  1. LICENSES/vendor/github.com/go-openapi/swag/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 May 08 04:49:00 GMT 2020
    - 11.2K bytes
    - Viewed (0)
  2. LICENSES/vendor/cloud.google.com/go/compute/metadata/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 May 26 17:20:33 GMT 2023
    - 11.2K bytes
    - Viewed (0)
  3. LICENSES/vendor/github.com/NYTimes/gziphandler/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: Wed Feb 03 21:57:36 GMT 2021
    - 11.2K bytes
    - Viewed (0)
  4. LICENSES/vendor/go.etcd.io/etcd/client/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: Fri Apr 05 09:05:09 GMT 2024
    - Last Modified: Tue Jun 15 14:06:09 GMT 2021
    - 11.2K bytes
    - Viewed (0)
  5. LICENSES/vendor/github.com/grpc-ecosystem/go-grpc-prometheus/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.27.md

    - The Kubernetes API server now correctly detects and closes existing TLS connections when its client certificate file for kubelet authentication has been rotated. ([#115315](https://github.com/kubernetes/kubernetes/pull/115315), [@enj](https://github.com/enj)) [SIG API Machinery, Auth, Node and Testing]
    Plain Text
    - Registered: Fri May 03 09:05:14 GMT 2024
    - Last Modified: Tue Apr 16 15:20:21 GMT 2024
    - 434.3K bytes
    - Viewed (3)
  7. .github/PULL_REQUEST_TEMPLATE.md

    /kind api-change
    /kind deprecation
    /kind failing-test
    /kind flake
    /kind regression
    -->
    
    #### What this PR does / why we need it:
    
    #### Which issue(s) this PR fixes:
    <!--
    *Automatically closes linked issue when PR is merged.
    Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
    _If PR is about `failing-tests or flakes`, please post the related issues/tests in a comment and do not use `Fixes`_*
    -->
    Fixes #
    Plain Text
    - Registered: Fri May 03 09:05:14 GMT 2024
    - Last Modified: Sun Aug 01 08:59:21 GMT 2021
    - 2.8K bytes
    - Viewed (0)
  8. LICENSES/vendor/go.opencensus.io/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: Wed Jul 01 20:12:36 GMT 2020
    - 11.2K bytes
    - Viewed (0)
  9. LICENSES/vendor/go.etcd.io/etcd/server/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)
  10. LICENSES/vendor/github.com/soheilhy/cmux/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 12 09:05:11 GMT 2024
    - Last Modified: Fri May 08 04:49:00 GMT 2020
    - 11.2K bytes
    - Viewed (0)
Back to top