| Age | Commit message (Collapse) | Author |
|---|
|
reported by Denis Fondras <openbsd at ledeuns dot net>
|
|
millert@ and jmc@ agree that "overriden" is wrong
|
|
|
|
the hint returned is over VM_MAXUSER_ADDRESS, apparently; better be safe for
now while this is investigated further.
|
|
|
|
|
|
|
|
Emacs does.
ok florian@
|
|
a magic number 4 since sometimes we can't fit a single packet
(jumbo frame) into 4 clusters.
OK dlg
|
|
"Sync with RFC 7230-7235 phrases and IANA registered status codes.
ok reyk@"
|
|
|
|
ok reyk@
|
|
|
|
code that comes with them.
ok mikeb@, henning@
|
|
ok deraadt@
|
|
ok yasuoka@
|
|
ok florian@ henning@
|
|
ok reyk@
|
|
|
|
and no longer matches the desired output
|
|
|
|
|
|
|
|
The .Bf block can contain subblocks, so it has to render as an
element that can contain flow content. But <em> cannot contain
flow content, only phrasing content. Rendering .Em and .Bf differently
would by unfortunate, and closing out .Bf before subblocks and
re-opening it afterwards would merely complicate both the C code
of the program and the generated HTML code. Besides, converting
.Em to semantic HTML markup would require some content to be put
into <em> and some into <i>, but we cannot automatically distinguish
which is which, so strictly speaking, we can't use semantic HTML
here but have to fall back to physical markup. Wonders of HTML...
|
|
Not hooked to the build yet because there are still too many bugs.
|
|
Note that we use 240u := 1i for all devices, even -Tps and -Tpdf.
Big fix of -Tascii rendering of f, m, and u.
Small fix of -Tascii rendering of c.
Big fix of -Thtml rendering of u.
Big fix of -Tps rendering of m, p, and u.
Clarify -Tps rendering of c.
Correct documentation of scaling units, in particular with respect to u.
This for example improves rendering of the OpenGL manuals.
Joint work with kristaps@.
|
|
|
|
PATH_INFO.
Therefore put a lower bound of strlen(root) on scriptlen.
This makes perfect sense for virtual FastCGI scripts which run chrooted
in another directory from httpd.
ok reyk@
|
|
ok dlg@
|
|
need a temporary path variable. Based on an initial diff from
chrisz@.
"Commit any failsafe version and I'm ok with it" chrisz@
|
|
The vast majority of .Em in real-world manuals is stress emphasis,
for which <em> is the correct markup. Admittedly, there are some
instances of .Em usage for alternate quality, for which <i> would
be a better match. Most of these are technical terms that neither
allow semantic markup nor are keywords - for the latter, .Sy would
be preferable. A typical example is that the shell breaks input into
.Em words .
Alternate voice or mood, which would also require <i>, is almost
absent from manuals.
We cannot satisfy both stress emphasis and alternate quality, so
pick the one that fits more often and looks less wrong when off.
Patch from Guy Harris <guy at alum dot mit dot edu>.
ok bentley@ joerg@NetBSD
|
|
Active Discovery Terminate packets.
ok mikeb@, henning@, phessler@
|
|
diff from benno@.
ok benno@, florian@
|
|
|
|
without this fix httpd always put at least the first
path component in SCRIPT_NAME even when it did not exist.
Now for completely non-existant paths everything goes into
PATH_INFO.
|
|
ok millert@
|
|
|
|
9 series LP/Wildcat Point-LP entries.
ok millert@
|
|
case of failing to map the 2nd object.
found by Paul Maurers
|
|
|
|
handling the error.
|
|
original OpenSSL commit message follows:
Fixed as shown; to be released post-1.0.2
commit bebbb11d132cc149f7713d6693703f8bfae10072
Author: Ingo Schwarze <schwarze@usta.de>
Date: Sat Jan 18 11:46:25 2014 +0100
RT3239: Extra comma in NAME lines of two manpages
In two OpenSSL manual pages, in the NAME section, the last word of the
name list is followed by a stray trailing comma. While this may seem
minor, it is worth fixing because it may confuse some makewhatis(8)
implementations.
While here, also add the missing word "size" to the one line
description in SSL_CTX_set_max_cert_list(3).
Reviewed by: Dr Stephen Henson <shenson@drh-consultancy.co.uk>
|
|
allocation strategy to VM_PSTRAT_BIGFIRST.
|
|
|
|
specifying a unit, the implied unit is 'n' (on the terminal, one
character position; in PostScript, half of the current font size
in points), not 'u' (roff output device basic unit). No functional
change right now, but important for the upcoming scaling unit fixes.
|
|
an equivalent number as its argument, and strlen() measures the width
of a string in characters, not in basic units. No functional change
right now, but important for the upcoming scaling unit fixes.
|
|
anchors for "once" rules: "In case this is the only rule in the
anchor, the anchor will be destroyed automatically after the rule
is matched." Employ an additional pointer pair to keep track of
the parent ruleset containing the anchor that we want to remove.
OK henning
|
|
Without the cast/mask, the compiler is allowed to optimize this directly
to the correct CPU intrinsic for rotate.
|
|
that owns the anchor on the pf anchor stack. There's no reason why we
should check for depth here. As a side effect this makes sure that the
correct nested anchor gets it's counter bumped instead of the top most.
For the save/restore symmetry pf_step_out_of_anchor is made to always
restore previous value of the anchor rule. depth == 0 means what we a
at the top (main ruleset).
OK henning
|
|
start with a ruleset pointer assigned to pf_main_ruleset so that
pf_purge_rule doesn't get called with a NULL.
Prompted by the discussion with Alexandr Nedvedicky <alexandr !
nedvedicky at oracle ! com>.
OK henning
|
