New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PR - Issue 49678 - organiSational vs organiZational spelling in lib389 #2740
Comments
Comment from spichugi (@droideck) at 2018-05-13 15:54:47 Looks good to me! Ack |
Comment from vashirov (@vashirov) at 2018-05-21 10:44:21 rebased onto 8c255f2f34f24313ca092daa13c6c4526377e809 |
Comment from vashirov (@vashirov) at 2018-05-21 13:01:39 @kenoh, I've added missing fixes for tests. |
Comment from vashirov (@vashirov) at 2018-05-21 15:31:31 rebased onto c6ac3cd4762c09a05ddb85dec126fa960237e851 |
Comment from vashirov (@vashirov) at 2018-05-22 17:07:14 rebased onto 4525b23652850552b094bff3f421d8e35cacf61e |
Comment from mhonek (@kenoh) at 2018-05-23 14:33:40 ACK from me. Just a last one missed probably due to a recent change Simon did, in |
Comment from vashirov (@vashirov) at 2018-05-23 16:01:36 rebased onto c1e022d |
Comment from vashirov (@vashirov) at 2018-05-23 16:02:23 Nice catch! Fixed it as well. |
Comment from vashirov (@vashirov) at 2018-05-23 16:03:05 Pull-Request has been merged by vashirov |
Patch |
Cloned from Pagure Pull-Request: https://pagure.io/389-ds-base/pull-request/49681
Bug description:
RFC4519 defines 'organization' object class using Oxford spelling.
It is common for academic, formal, and technical writing for an
international readership. We should be following common spelling
in function names and methods, otherwise it is confusing
and annoying to remember which one is used where.
Fix description:
Use Oxford spelling for 'organization' and 'organizationalUnit'.
Resolves: #2737
Reviewed by: ???
The text was updated successfully, but these errors were encountered: