summaryrefslogtreecommitdiff
path: root/TODO
diff options
context:
space:
mode:
authorFrantisek Sumsal <frantisek@sumsal.cz>2023-04-20 21:54:59 +0200
committerFrantisek Sumsal <frantisek@sumsal.cz>2023-04-20 21:54:59 +0200
commit94d82b59807488343bd206ba8f111d24ff17d9c1 (patch)
tree7df4d9d1e1f45ad8d82bbcee498a4e415dd06761 /TODO
parentff707dd1b1a6bd49e7f693564ec204f23ad23a7d (diff)
downloadsystemd-94d82b59807488343bd206ba8f111d24ff17d9c1.tar.gz
tree-wide: code spelling fixes
As reported by Fossies.
Diffstat (limited to 'TODO')
-rw-r--r--TODO6
1 files changed, 3 insertions, 3 deletions
diff --git a/TODO b/TODO
index 19a2535e1b..ea35f3b7db 100644
--- a/TODO
+++ b/TODO
@@ -134,7 +134,7 @@ Features:
allow the host to read it, while making everything read-only.
* fix our various hwdb lookup keys to end with ":" again. The original idea was
- that hwdb patters can match arbitrary fields with expressions like
+ that hwdb patterns can match arbitrary fields with expressions like
"*:foobar:*", to wildcard match both the start and the end of the string.
This only works safely for later extensions of the string if the strings
always end in a colon. This requires updating our udev rules, as well as
@@ -142,7 +142,7 @@ Features:
* mount /tmp/ and /var/tmp with a uidmap applied that blocks out "nobody" user
among other things such as dynamic uid ranges for containers and so on. That
- way noone can create files there with these uids and we enforce they are only
+ way no one can create files there with these uids and we enforce they are only
used transiently, never persistently.
* rework loopback support in fstab: when "loop" option is used, then
@@ -188,7 +188,7 @@ Features:
* journald: also collect CLOCK_BOOTTIME timestamps per log entry. Then, derive
"corrected" CLOCK_REALTIME information on display from that and the timestamp
- info of the newest entry of the specificy boot (as identified by the boot
+ info of the newest entry of the specific boot (as identified by the boot
ID). This way, if a system comes up without a valid clock but acquires a
better clock later, we can "fix" older entry timestamps on display, by
calculating backwards. We cannot use CLOCK_MONOTONIC for this, since it does