+* journald: also get thread ID from client, plus thread name
+
+* check if we can make journalctl by default use --follow mode inside of less if called without args?
+
+* Addd a verbose mode to "systemctl start" and friends that explains what is being done or not done
+
+* "systemctl is-failed" to join "systemctl is-active" and "systemctl is-enabled".
+
+* journal is not closed properly at shutdown when run in a container?
+
+* All log messages generated from socket.c, service.c, ... should
+ include _SYSTEMD_UNIT= fields so that "systemctl status" can show
+ them along with the unit
+
+* define a message ID for "overmounting non-empty directory" and write message catalog entry for it
+
+* use polkit "imply" for binding hostname actions together
+
+* journal: when waiting for journal additions always sleep at least 1s or so, in order to minimize wakeups
+
+* When shutdown.target is queued begin with an asynchronous sync()?
+
+* Add ConditionBatteryPower= or ConditionACPower=? (but definitely not both)
+
+* add API to close/reopen/get fd for journal client fd in libsystemd-journal.
+
+* maybe add API to send pairs of iovecs via sd_journal_send
+
+* fallback to /dev/log based logging in libsystemd-journal, if we can't log natively?
+
+* declare the local journal protocol stable in the wiki interface chart
+
+* journal: reuse XZ context
+
+* sd-journal: speed up sd_journal_get_data() with transparent hash table in bg
+
+* introduce ntp.service (or suchlike) as symlink that is used to arbitrate between various NTP implementations
+
+* timer units should get the ability to trigger when:
+ - CLOCK_REALTIME makes jumps (TFD_TIMER_CANCEL_ON_SET)
+ - DST changes
+
+* update the kernel's TZ (sys_tz) when DST changes
+
+* sync down the system time to the RTC when:
+ - CLOCK_REALTIME makes jumps (the user explicitely requested a time set)
+ - DST/timezone changes && ntp is active && RTC-in-localtime (never do it without ntp)
+ This takes care of syncing ntpdate updates to the RTC, and DST updates for localtime
+ mode, it will never touch the RTC if the no reliable time source is active or the
+ user did not request anything like it.