Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 26 for syntax (0.18 sec)

  1. licenses/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: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Jul 17 20:25:52 GMT 2023
    - 11.1K bytes
    - Viewed (0)
  2. licenses/google.golang.org/genproto/googleapis/api/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: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Thu Jun 01 21:17:01 GMT 2023
    - 11.1K bytes
    - Viewed (0)
  3. licenses/go.opentelemetry.io/otel/sdk/metric/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: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Jul 17 20:25:52 GMT 2023
    - 11.1K bytes
    - Viewed (0)
  4. licenses/istio.io/client-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: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Tue Oct 31 18:53:28 GMT 2023
    - 11.1K bytes
    - Viewed (0)
  5. licenses/istio.io/api/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: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Tue Oct 31 18:53:28 GMT 2023
    - 11.1K bytes
    - Viewed (0)
  6. licenses/sigs.k8s.io/yaml/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: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Tue Oct 31 19:53:28 GMT 2023
    - 15.8K bytes
    - Viewed (0)
  7. 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: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Tue Oct 31 14:48:35 GMT 2023
    - 11.1K bytes
    - Viewed (0)
  8. licenses/go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp/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: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Fri Dec 15 21:30:37 GMT 2023
    - 11.1K bytes
    - Viewed (0)
  9. licenses/go.opentelemetry.io/otel/sdk/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: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Jul 17 20:25:52 GMT 2023
    - 11.1K bytes
    - Viewed (0)
  10. licenses/cloud.google.com/go/auth/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: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Tue Apr 30 13:56:46 GMT 2024
    - 11.1K bytes
    - Viewed (0)
Back to top