- Sort Score
- Result 10 results
- Languages All
Results 91 - 100 of 643 for printed (0.15 sec)
-
licenses/sigs.k8s.io/kustomize/api/LICENSE
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. Copyright {yyyy} {name of copyright owner} Licensed under the Apache License, Version 2.0 (the "License");
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Thu Apr 22 22:59:25 UTC 2021 - 11.1K bytes - Viewed (0) -
licenses/sigs.k8s.io/mcs-api/LICENSE
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. Copyright {yyyy} {name of copyright owner} Licensed under the Apache License, Version 2.0 (the "License");
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Fri Mar 12 21:17:55 UTC 2021 - 11.1K bytes - Viewed (0) -
licenses/sigs.k8s.io/structured-merge-diff/v4/LICENSE
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. Copyright {yyyy} {name of copyright owner} Licensed under the Apache License, Version 2.0 (the "License");
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Sun Aug 30 14:15:49 UTC 2020 - 11.1K bytes - Viewed (0) -
licenses/github.com/docker/distribution/LICENSE
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. Copyright {yyyy} {name of copyright owner} Licensed under the Apache License, Version 2.0 (the "License");
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Sat Oct 26 02:47:39 UTC 2019 - 11.1K bytes - Viewed (0) -
licenses/github.com/go-logr/stdr/LICENSE
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. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License");
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Mon Jul 17 20:25:52 UTC 2023 - 11.1K bytes - Viewed (0) -
licenses/github.com/go-openapi/jsonreference/LICENSE
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. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License");
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Sat Oct 26 02:47:39 UTC 2019 - 11.1K bytes - Viewed (0) -
licenses/github.com/google/btree/LICENSE
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. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License");
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Sat Oct 26 02:47:39 UTC 2019 - 11.1K bytes - Viewed (0) -
LICENSE
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. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License");
Registered: Tue Nov 05 12:39:12 UTC 2024 - Last Modified: Mon Nov 29 17:31:56 UTC 2021 - 13.3K bytes - Viewed (0) -
licenses/github.com/google/cel-go/LICENSE
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. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License");
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Wed Mar 23 01:29:36 UTC 2022 - 12.7K bytes - Viewed (0) -
licenses/sigs.k8s.io/json/LICENSE
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. Copyright {yyyy} {name of copyright owner} Licensed under the Apache License, Version 2.0 (the "License");
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Wed Jan 05 01:31:25 UTC 2022 - 12.6K bytes - Viewed (0)