Search Options

Results per page
Sort
Preferred Languages
Advance

Results 31 - 40 of 62 for syntax (0.19 sec)

  1. LICENSES/vendor/github.com/coreos/go-systemd/v22/LICENSE

    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: Wed Jun 16 15:14:16 GMT 2021
    - 10.2K bytes
    - Viewed (0)
  2. LICENSES/vendor/github.com/containerd/cgroups/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: Tue May 19 23:53:55 GMT 2020
    - 11.2K bytes
    - Viewed (0)
  3. LICENSES/vendor/github.com/checkpoint-restore/go-criu/v5/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: Thu May 20 06:51:59 GMT 2021
    - 11.2K bytes
    - Viewed (0)
  4. 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)
  5. 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)
  6. LICENSES/vendor/github.com/google/cel-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: Tue Mar 08 01:47:04 GMT 2022
    - 12.9K bytes
    - Viewed (0)
  7. LICENSES/vendor/go.etcd.io/etcd/raft/v3/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: Tue Jun 15 14:06:09 GMT 2021
    - 11.2K bytes
    - Viewed (0)
  8. 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)
  9. LICENSES/vendor/go.etcd.io/etcd/client/v3/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: Tue Jun 15 14:06:09 GMT 2021
    - 11.2K bytes
    - Viewed (0)
  10. LICENSES/vendor/github.com/matttproud/golang_protobuf_extensions/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 19 09:05:10 GMT 2024
    - Last Modified: Fri May 08 04:49:00 GMT 2020
    - 11.3K bytes
    - Viewed (0)
Back to top