Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 12 for syntax (0.27 sec)

  1. LICENSES/vendor/github.com/google/gnostic-models/LICENSE

          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
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    Plain Text
    - Registered: Fri Apr 26 09:05:10 GMT 2024
    - Last Modified: Fri Jun 02 14:34:25 GMT 2023
    - 11.2K bytes
    - Viewed (0)
  2. LICENSES/vendor/cloud.google.com/go/compute/metadata/LICENSE

          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
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    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. CHANGELOG/CHANGELOG-1.27.md

      - https://github.com/kubernetes-sigs/kustomize/issues/4731: Remove a potential build-time side-effect in ConfigMapGenerator...
    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)
  4. LICENSES/vendor/github.com/google/s2a-go/LICENSE

          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
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    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)
  5. LICENSES/vendor/github.com/go-logr/stdr/LICENSE

          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
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    Plain Text
    - Registered: Fri May 03 09:05:14 GMT 2024
    - Last Modified: Sun Sep 18 01:47:24 GMT 2022
    - 11.2K bytes
    - Viewed (0)
  6. LICENSES/vendor/github.com/distribution/reference/LICENSE

          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
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    Plain Text
    - Registered: Fri May 03 09:05:14 GMT 2024
    - Last Modified: Fri Sep 01 01:53:40 GMT 2023
    - 11.2K bytes
    - Viewed (0)
  7. LICENSES/vendor/github.com/googleapis/enterprise-certificate-proxy/LICENSE

          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
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    Plain Text
    - Registered: Fri Apr 26 09:05:10 GMT 2024
    - Last Modified: Fri May 26 17:20:33 GMT 2023
    - 11.3K bytes
    - Viewed (0)
  8. LICENSES/vendor/github.com/moby/ipvs/LICENSE

          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
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    Plain Text
    - Registered: Fri Apr 26 09:05:10 GMT 2024
    - Last Modified: Sat Jan 14 21:13:24 GMT 2023
    - 11.2K bytes
    - Viewed (0)
  9. LICENSES/vendor/cloud.google.com/go/compute/LICENSE

          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
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    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)
  10. LICENSES/vendor/go.opentelemetry.io/contrib/instrumentation/github.com/emicklei/go-restful/otelrestful/LICENSE

          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
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    Plain Text
    - Registered: Fri Apr 05 09:05:09 GMT 2024
    - Last Modified: Sun Sep 18 01:47:24 GMT 2022
    - 11.3K bytes
    - Viewed (0)
Back to top