- Sort Score
- Result 10 results
- Languages All
Results 41 - 50 of 105 for comments (0.47 sec)
-
CHANGELOG/CHANGELOG-1.5.md
* Removed comments in json config when using kubectl edit with -o json ([#31685](https://github.com/kubernetes/kubernetes/pull/31685), [@jellonek](https://github.com/jellonek))
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Thu Dec 24 02:28:26 GMT 2020 - 136.4K bytes - Viewed (1) -
CHANGELOG/CHANGELOG-1.22.md
- YAML documents separators ("---") can now be followed by whitespace and comments ("# ....") on the same line. This fixes a bug where documents starting with a comment after the separator were ignored. Other types of content on the same line will result in an error. ([#103457](https://github.com/kubernetes/kubernetes/pull/103457), [@codearky](https://github.com/codearky))...
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Tue Dec 13 12:43:45 GMT 2022 - 454.1K bytes - Viewed (1) -
LICENSES/third_party/forked/gotestsum/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
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Fri Apr 01 18:49:15 GMT 2022 - 11.1K bytes - Viewed (0) -
LICENSES/vendor/go.etcd.io/etcd/pkg/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
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) -
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
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) -
LICENSES/vendor/github.com/opencontainers/selinux/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
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) -
LICENSES/vendor/github.com/grpc-ecosystem/go-grpc-middleware/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
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) -
LICENSES/vendor/github.com/prometheus/client_golang/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
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) -
LICENSES/vendor/github.com/coredns/corefile-migration/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
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) -
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)