Search Options

Results per page
Sort
Preferred Languages
Advance

Results 41 - 50 of 297 for unclosed4 (0.11 sec)

  1. licenses/github.com/prometheus/client_golang/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
    Registered: Fri Jun 14 15:00:06 UTC 2024
    - Last Modified: Sat Oct 26 02:47:39 UTC 2019
    - 11.1K bytes
    - Viewed (0)
  2. licenses/sigs.k8s.io/kustomize/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
    Registered: Fri Jun 14 15:00:06 UTC 2024
    - Last Modified: Thu Apr 22 22:59:25 UTC 2021
    - 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
    Registered: Fri Jun 14 15:00:06 UTC 2024
    - Last Modified: Fri Mar 12 21:17:55 UTC 2021
    - 11.1K bytes
    - Viewed (0)
  4. licenses/sigs.k8s.io/structured-merge-diff/v4/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
    Registered: Fri Jun 14 15:00:06 UTC 2024
    - Last Modified: Sun Aug 30 14:15:49 UTC 2020
    - 11.1K bytes
    - Viewed (0)
  5. src/vendor/golang.org/x/text/unicode/bidi/bracket.go

    // Identify the bracket pairs in the current isolating run sequence
    // according to BD16. For each bracket-pair element in the list of pairs of
    // text positions:
    //
    // a Inspect the bidirectional types of the characters enclosed within the
    // bracket pair.
    //
    // b If any strong type (either L or R) matching the embedding direction is
    // found, set the type for both brackets in the pair to match the embedding
    // direction.
    //
    Registered: Wed Jun 12 16:32:35 UTC 2024
    - Last Modified: Fri Apr 26 19:27:51 UTC 2019
    - 11.2K bytes
    - Viewed (0)
  6. LICENSES/vendor/github.com/prometheus/client_golang/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
    Registered: Sat Jun 15 01:39:40 UTC 2024
    - Last Modified: Fri May 08 04:49:00 UTC 2020
    - 11.2K bytes
    - Viewed (0)
  7. 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
    Registered: Sat Jun 15 01:39:40 UTC 2024
    - Last Modified: Fri May 08 04:49:00 UTC 2020
    - 11.2K bytes
    - Viewed (0)
  8. LICENSES/vendor/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
    Registered: Sat Jun 15 01:39:40 UTC 2024
    - Last Modified: Fri May 26 17:20:33 UTC 2023
    - 11.2K bytes
    - Viewed (0)
  9. LICENSES/vendor/gopkg.in/square/go-jose.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
    Registered: Sat Jun 15 01:39:40 UTC 2024
    - Last Modified: Fri May 08 04:49:00 UTC 2020
    - 11.2K bytes
    - Viewed (0)
  10. LICENSES/vendor/sigs.k8s.io/structured-merge-diff/v4/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
    Registered: Sat Jun 15 01:39:40 UTC 2024
    - Last Modified: Mon Aug 10 22:35:23 UTC 2020
    - 11.2K bytes
    - Viewed (0)
Back to top