[MDEV-29275] typos (debian, Docs, include) Created: 2022-08-08 Updated: 2022-12-20 Resolved: 2022-12-20 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Documentation |
| Fix Version/s: | 10.3.38, 10.4.28, 10.5.19, 10.6.12, 10.7.8, 10.8.7, 10.9.5, 10.10.3 |
| Type: | Task | Priority: | Minor |
| Reporter: | Eric Lindblad (Inactive) | Assignee: | Ian Gilfillan |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
debian any of these files maintained outside the repo some of the content in mariadb-server.postinst may be 15+ years old since opening the ticket the path on the first sed command was corrected
Docs
include could be rewritten (awkward comment)
should any headers not be edited owing to copyrights since opening the ticket the spelling as 'general' was corrected
|
| Comments |
| Comment by Eric Lindblad (Inactive) [ 2022-08-08 ] | ||||||||||||
|
incidentally the spelling forceintervall/intervall/intervalls (.c, .h and .result files) and uppdated/uppdates (.c and .test files) is likely due to incorrect translation from Swedish, and, would corrections forceinterval/interval/intervals be authorised updated/updates solely appears in comments
| ||||||||||||
| Comment by Otto Kekäläinen [ 2022-08-31 ] | ||||||||||||
|
I pushed the debian/* ones to https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/ce555423817cf8e638296c2387615d6f363b99e2 but ideally all of these would be fixed upstream in MariaDB. | ||||||||||||
| Comment by Eric Lindblad (Inactive) [ 2022-08-31 ] | ||||||||||||
|
had the wrong path in my sed command (this is now corrected)
the push to debian appears not to have affected the lintian-overrides file
the misspelling as 'formated' appears elsewhere
| ||||||||||||
| Comment by Daniel Black [ 2022-12-20 ] | ||||||||||||
|
Thanks to musvaage the headers and debian directories have been fixed:
"formated"/"uppdate" still remains. | ||||||||||||
| Comment by Daniel Black [ 2022-12-20 ] | ||||||||||||
|
Making as closed. Remaining fixes seem code related. Although code fixing can be done, its harder especially if a missed change occurs on a later version than the fix resulting in a compile failure which causes more pain than the existing misspelling. If you fix the latest version, a bug fix later on the earlier version all of a sudden needs a different fix in the latest version if it touches a misspelt word. If you can be exceptionally meticulous of compiling and running the test suite on all versions you may attempt it, but please don't get it wrong, it consumes time of developers that could be expending fixing more user visible problems. My current feeling is I'd rather code misspellings be left as is. |