| Age | Commit message (Collapse) | Author |
|---|
|
'Looks right' deraadt@
|
|
|
|
still broken in mandoc 1.9.14, fix being sent to kristaps@.
Path names (.Pa) are usually underlined, except below .Bl -inset, -hang,
-ohang, -tag or -column in the FILES section (yuck).
Note that .Bl -bullet is subtly broken in an urelated way:
That will need fixing as well before this test can fully succeed.
|
|
mandoc 1.9.14 still fails this one, patch being sent to kristaps@.
The groff .Bl -column spacing we are trying to follow is weird:
with less than 5 columns, groff puts 4 blanks between columns;
with exactly 5 columns, groff puts 3 blanks between columns;
with more than 5 columns, and also with more than 78 characters per line,
groff usually falls over and bites the dust - though the exact failures
look rather different in various cases, and a few cases even work...
No use trying to test anything for more than 5 columns, though.
|
|
|
|
is sensitive to changes in struct proc.
fixes for warnings and ok nicm@
|
|
Still broken in 1.9.14, fix being sent to kristaps@.
|
|
|
|
Theo.
|
|
they're still unused months later and there's many ways to achieve having a
set of priorities on envelopes without needing additionnal queues.
|
|
- handle .ie, .el minimally
- define \(aq as the ' symbol.
|
|
|
|
point people at where they should be looking instead.
ok espie@
|
|
instead, install a timeout(9) to run the queue. fixes a panic
reported by wilfried@
|
|
as neither arrayified not arrayfied exist -- sanctioned dictionaries
like Merriam-Webster ones suggest a few alternatives (e.g., arrayed),
however these made up words are easy to understand and we are not
certain that current ones are not ok.
ok jmc@
|
|
|
|
|
|
on. use the received-on IFNAME filter option on a pf.conf rule to restrict
which packet the interface had to be received on. eg:
pass out on em0 from $foo to $bar received-on fxp0
ive been running this in production for a week now. i find it particularly
usefull with interface groups.
no objections, and a few "i like"s from henning, claudio, deraadt, mpf
|
|
- new function a2roffdeco
- font modes (\f) only affect the current stack point
- implement scaling (\s)
- implement space suppression (\c)
- implement non-breaking space (\~) in -Tascii
- many manual improvements
|
|
fails with 1.9.13, succeeds with 1.9.14
|
|
correctness/functionality:
- bugfix: properly ignore lines with only a dot in -man
- bugfix: .Bl -ohang doesn't allow -width, warn about this
- improve date string handling by new function mandoc_a2time
- some HTML improvements
- significant documentation additions in man.7 and mdoc.7
portability:
- replace __dead by __attribute__((noreturn))
- bugfix: correct .Dx rendering
- some more library names for NetBSD
simplicity:
- replace hand-rolled putchar(3)-loops by fwrite(3)
- replace single-character printf(3) by putchar(3)
|
|
ok miod@
|
|
|
|
This restructures the client_* API internals significantly. The code becomes
pipelining in nature. All SMTP commands are put on the output queue and
dequeued as quickly as possible. Once dequeued, they're moved to the receive
queue so that replies can be matched with previous commands.
Dequeuing commands from the output queue halts when the count of commands
currently in-pipeline (``cmdi'') is equal to the command send window (``cmdw'').
There are three cmdw values useful in practice:
0 clear pipeline, ie. inhibit all future sends
1 disable pipelining, ie. use old ``one-request-one-reply`` mode
SIZE_T_MAX enable pipelining, ie. dequeue as many commands as possible
At the beginning of session cmdw is 1. When it is found that peer supports
PIPELINING, it grows to SIZE_T_MAX. After dequeing DATA it is again 1. After
sending QUIT it is 0.
Each command dequeued from the output queue becomes a buf in a msgbuf. The act
of combining multiple commands into a single send operation did not need to be
implemented: buf_write() already combines bufs using iovec and sends them at
once using sendmsg(2).
Tested by todd@ and oga@
"looks good" to gilles@
|
|
address for so that the device is no considered unnumbered.
|
|
so put it in struct process instead of struct proc. While at it,
move the p_emul member inside struct proc so that it gets copied
automatically instead of requiring manual assignment.
ok deraadt@
|
|
|
|
correctness/functionality:
- bugfix: do not die when overstep hits the right margin
- new option: -fign-escape
- and various HTML features
portability:
- replace bzero(3) by memset(3), which is ANSI C
- replace err(3)/warn(3) by perror(3)/exit(3), which is ANSI C
- iuse argv[0] instead of __progname
- add time.h to various files for FreeBSD compilation
simplicity:
- do not allocate header/footer data dynamically in *_term.c
- provide and use malloc frontends that error out on failure
for full changelogs, see http://bsd.lv/cgi-bin/cvsweb.cgi/
|
|
|
|
|
|
patch from Daniel Dickman <didickman at gmail dot com> tweaked by me;
"looks ok" millert@, manual help and ok jmc@
|
|
in almost all sockaddr_in6 addresses it is required for the nexthop and
sin6_scope_id is actually ignored there.
This needs to be fixed but my quota of IPv6 insanity is already used for today.
Workaround for now. My simple testsetup is now actually able to install
the first ospf6d learned routes in the kernel. Weeee!
|
|
this information to kroute and kroute can use that information to fill in
the various sin6_scope_id fields.
|
|
ok espie
|
|
|
|
|
|
definitions so that we have a chance to build a correct nexthop.
Insane that a struct in6_addr is unable to fully specify an IPv6 address.
kroute.c still needs fixing but now the rib is starting to make sense.
|
|
ok claudio
|
|
again but different because of link local addressing.
|
|
interface id of the remote side. Found the hard way.
|
|
We need to pass our ifindex so that we can find the Link-LSA that has the
link local address stored for that router. Don't we all like IPv6 link local
addresses and their insanity.
|
|
|
|
|
|
This way, the first time sysmerge is run on a new box, it will already
have reference sums needed for automatic processing.
Original idea from and discussed with deraadt@
"commit it" deraadt@, tweaks and ok millert
|
|
|
|
|
|
|
|
properly and choose the correct last window after a window is killed.
|
|
default DAC receive the first playback stereo channel pair if the DAC
wouldn't otherwise be used and allow the jack's output volume to be
controlled by outputs.master by default. this was already mostly
implemented for codecs with 3 or more dacs, but front headphone jacks
are also common on 2 dac codecs as well.
|
|
|
