| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
device-provided information easier.
Add support for a few more devices.
Trigger state machine updates quickly so as not to have to wait 6 seconds to
get the device identified, then 6 more seconds to get the first sensor data.
Tested on:
TEMPerX_V3.3 by landry@
TEMPerF1.4M by sthen@
TEMPerHUM_V4.0, TEMPer2_V4.1, TEMPer1F_V4.1 and TEMPerGold_V3.4 by yours truly
|
|
|
|
prodding pb
OK phessler, sthen
Input & OK jmc
|
|
|
|
objdir by now.
|
|
|
|
Build and install the tzdata.zi file and build the leapseconds file
from leap-seconds.list (installing both versions). Third-party
software now expects these files to be installed. OK sthen@ deraadt@
|
|
ok plus various improvements to the text by tb@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Suggested by espie@
While here, sprinkle more .Ev.
|
|
ok tb@
|
|
Tweak from kn@
OK landry@ kn@
|
|
ok op@
+1 rsadowski
|
|
While these versions of gcc don't have full C99 support, it is
better than defaulting to C89 when building modern software.
OK deraadt@
|
|
There has been some unexpected fallout. Requested by deraadt@.
|
|
While these versions of gcc don't have full C99 support, it is
better than defaulting to C89 when building modern software.
OK deraadt@
|
|
It appears the Linux Manual Pages project started to quite aggressively
use .TQ ever for cases where it not only provides no value, but makes
formatting worse even when it formats as intended. It's also a bad idea
to use it that aggressively because .TQ has particularly catastrophic
formatting behaviour on formatters (other than groff and mandoc) that do
not support it: It essentially has the effect of omitting the topic of
the discussion from the formatted version of the manual page, but in
such a way that it does not become apparent to the reader that anything
is missing.
But whether this is wise or stupid is their problem and none of our
business. Either way, we should not call a thing "rarely used"
after that is no longer true.
Thanks to Alejandro Colomar <alx at kernel org org>
for making me aware that the statement is no longer true.
|
|
inside \w arguments, and skip most other escape sequences when measuring
the output length in this way because most escape sequences contribute
little or nothing to text width: for example, consider font escapes in
terminal output.
This implementation is very rudimentary. In particular, it assumes that
every character has the same width. No attempt is made to detect
double-width or zero-width Unicode characters or to take dependencies on
output devices or fonts into account. These limitations are hard to
avoid because mandoc has to interpolate \w at the parsing stage when the
output device is not yet known. I really do not want the content of the
syntax tree to depend on the output device.
Feature requested by Paul <Eggert at cs dot ucla dot edu>, who also
submitted a patch, but i chose to commit this very different patch
with almost the same functionality.
His input was still very valuable because complete support for \w is
out of the question, and consequently, the main task is identifying
subsets of the feature that are needed for real-world manual pages
and can be supported without uprooting the whole forest.
|
|
|
|
before.
Noted by Marko Cupac, thanks.
|
|
|
|
ok ratchov@, kn@
|
|
|
|
|
|
Add a TIMEOUT_MPSAFE flag to signal that a timeout is safe to run
without the kernel lock. Currently, TIMEOUT_MPSAFE requires
TIMEOUT_PROC. When the softclock() is unlocked in the future this
dependency will be removed.
On MULTIPROCESSOR kernels, softclock() now shunts TIMEOUT_MPSAFE
timeouts to a dedicated "timeout_proc_mp" bucket for processing by the
dedicated softclock_thread_mp() kthread. Unlike softclock_thread(),
softclock_thread_mp() is not pinned to any CPU and runs run at IPL_NONE.
Prompted by bluhm@. Lots of input from bluhm@. Joint work with mvs@.
Prompt: https://marc.info/?l=openbsd-tech&m=169646019109736&w=2
Thread: https://marc.info/?l=openbsd-tech&m=169652212131109&w=2
ok mvs@
|
|
|
|
It is supported by all major man(7) implementations that G. Branden
Robinson and myself are aware of, so calling it "non-portable" can
no longer be justified. Using it becomes increasingly more common,
so calling it "non-standard" is now misleading. It is certainly
useful and not deprecated.
While here, also remove the word "non-standard" from the descriptions
of several other macros because it is slightly confusing. A formal
standard for the man(7) language does not exist. Arguably, Version 7
AT&T UNIX used to be a de-facto standard, but its influence has been
waning for 40 years, and various features that Version 7 did not
support are now widely used.
|
|
in bsd.port.mk that govern its behavior.
|
|
|
|
Restructure so that the most important information is first.
Describe how it modifies bsd.port.mk variables.
Document all public variables set by the module.
Rewrite prompted by feedback from schwarze@
Multiple rounds of review and many fixes from schwarze@
OK schwarze@
|
|
|
|
|
|
'ports' permits to force the use of ld.lld from lang/clang module.
ok landry@
|
|
reminded by pamela@
|
|
|
|
OK tb@
|
|
More than ten years ago, bsd.lib.mk stopped creating lib*_pic.a files
and the corresponding PFRAG.no_mips64 were removed from the ports tree.
Last year the -Dno_mips64 handling in bsd.port.mk was GC'd too, but the
note in the bsd.port.mk manpage was left.
ok espie@
|
|
Enabling REGRESS_FAIL_EARLY made REGRESS_LOG error out at the first error,
which is pointless. So default to no if REGRESS_LOG is set unless the user
explicitly enabled it.
Requested by claudio
ok bluhm
|
|
|
|
it as soon as my test bulk finishes.
|
|
|
|
|
