| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
See 3f9a0a522f2029e9295ea5e9984259022be88413 for justification.
|
| |
|
|
|
|
|
|
| |
This has the advantage that the executables are always in place and we don't
need any units to exist on the bus, so we can eventually hook this up into
a normal build system. (Probably as a build time check.)
|
|
|
|
|
|
| |
See d35f51ea848ca76bd3747db69e8c5dd864e82bc3 for justification.
First use in each file is turned into a link to the documentation page.
|
|
|
|
|
|
|
|
| |
Follow-up for f92c8d1c67bcdeba097e3203d8aafe3a31230ada.
directives.index:
- This index contains 3398 entries in 19 sections, referring to 333 individual
+ This index contains 4316 entries in 19 sections, referring to 333 individual
|
|
|
|
| |
For some reason I must've forgotten this page in 4fb222c4b2.
|
| |
|
|
|
|
| |
Also includes the issues pointed out by @boucman.
|
|
|
|
|
|
| |
Fixes #2562.
v2: the erroneous part about CAP_SYS_ADMIN is removed
|
|
|
|
|
|
| |
So far the units there were being documented had only one custom interface.
But for the pid1 case, something more flexibile is needed. So let's add
an annotation in the page what we want to print, and filter in the generator.
|
|
As usual, the formatting was fixed and various obvious updates
were done, but nothing major.
I removed documentation of snapshots and related methods though.
|