- Sort Score
- Result 10 results
- Languages All
Results 491 - 500 of 613 for description_ (0.14 sec)
-
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]
Registered: Sun Sep 07 03:35:12 UTC 2025 - Last Modified: Wed Sep 11 20:39:30 UTC 2013 - 11.1K bytes - Viewed (0) -
cmd/iam-object-store.go
iamOS.deleteIAMConfig(ctx, getMappedPolicyPath(user, userType, false)) } return u, errNoSuchUser } u.Credentials.Claims = jwtClaims.Map() } if u.Credentials.Description == "" { u.Credentials.Description = u.Credentials.Comment } return u, nil } func (iamOS *IAMObjectStore) loadUserConcurrent(ctx context.Context, userType IAMUserType, users ...string) ([]UserIdentity, error) {
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Fri Aug 29 02:39:48 UTC 2025 - 26.6K bytes - Viewed (0) -
LICENSES/vendor/cel.dev/expr/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]
Registered: Fri Sep 05 09:05:11 UTC 2025 - Last Modified: Wed Nov 06 20:53:17 UTC 2024 - 11.2K bytes - Viewed (0) -
LICENSES/vendor/github.com/coredns/caddy/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}
Registered: Fri Sep 05 09:05:11 UTC 2025 - Last Modified: Sun Jun 13 05:06:37 UTC 2021 - 11.2K bytes - Viewed (0) -
LICENSES/vendor/github.com/coredns/corefile-migration/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]
Registered: Fri Sep 05 09:05:11 UTC 2025 - Last Modified: Fri May 08 04:49:00 UTC 2020 - 11.2K bytes - Viewed (0) -
LICENSES/vendor/github.com/coreos/go-oidc/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}
Registered: Fri Sep 05 09:05:11 UTC 2025 - Last Modified: Fri May 08 04:49:00 UTC 2020 - 11.2K bytes - Viewed (0) -
LICENSES/vendor/github.com/distribution/reference/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}
Registered: Fri Sep 05 09:05:11 UTC 2025 - Last Modified: Fri Sep 01 01:53:40 UTC 2023 - 11.2K bytes - Viewed (0) -
LICENSES/vendor/github.com/go-logr/logr/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}
Registered: Fri Sep 05 09:05:11 UTC 2025 - Last Modified: Sat May 16 11:52:51 UTC 2020 - 11.2K 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]
Registered: Fri Sep 05 12:43:10 UTC 2025 - Last Modified: Wed Feb 22 18:59:39 UTC 2023 - 11.1K bytes - Viewed (0) -
docs/en/docs/management-tasks.md
* Create a new discussion with the title `Bosnian Translations` (or the language name in English) * A description of: ```Markdown ## Bosnian translations This is the issue to track translations of the docs to Bosnian. 🚀
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sat Nov 09 16:39:20 UTC 2024 - 14.2K bytes - Viewed (0)