Age | Commit message (Collapse) | Author |
|
|
|
|
|
ok kettenis millert otto
|
|
|
|
resolve the contradiction in the manual whether it's allowed or not
in favour of "not allowed" for now, shelving my diff to support
nested displays in mandoc(1) for later consideration.
Found by and unbreaking the build with mandoc(1).
Feedback and OK jmc@
|
|
not a grandchild. Thus, insert another level of .Bl.
Found by and unbreaking the build with mandoc(1).
OK jmc@
|
|
involving .It, so we cannot use .Bl -column here and switch to .Bd.
Found by and unbreaking the build with mandoc(1).
While here, reduce the indentation, it looks better.
OK jmc@
|
|
Found by and unbreaking the build with mandoc(1).
OK jmc@
|
|
Mention BCM5708S specifically as a Gigabit/2500 PHY.
|
|
|
|
|
|
|
|
|
|
|
|
many more medias, types and options. Input and OK sthen@ and jmc@
|
|
|
|
|
|
requested by cnst
|
|
files or directories when applicable.
The inspiration and name of MACHINE_CPU come from NetBSD, although the way to
provide it to Makefiles is completely different.
ok kettenis@
|
|
ok beck@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ok sthen@
|
|
|
|
|
|
their gizmo is supported. incomplete, but it can grow.
ok deraadt, some hints jmc
|
|
the changes in pppoe.4 are just to keep things consistent...
|
|
|
|
actions. Allow interfaces to be specified in special table entries for
the routing actions. Lists of addresses can now only be done using tables,
which pfctl will generate automatically from the existing syntax.
Functionally, this deprecates the use of multiple tables or dynamic
interfaces in a single nat or rdr rule.
ok henning dlg claudio
|
|
|
|
* remove bogus '\\' entry, it is not a correct way to render a backslash
* fix column width specifications (problem noted by jmc@
and cause found by kristaps@)
* mandoc_char(7) is not a utility (noticed by deraadt@)
* improve wording of first sentence (from jmc@)
* add OpenBSD RCS-Id (from jmc@)
* kill whitespace at EOLs (from jmc@)
ok kristaps@, "formatting looks good now" jmc@
|
|
- remove text concerning unsupported character device stuff
- remove text concerning unsupported RXIOC* ioctls
all of this stuff is from miod
|
|
files. If any information found in these documents is worthwhile and you
miss it, please make the time to work it into the manual pages (which people
actually do read).
ok guenther
|
|
man(7) and mdoc(7) special characters and predefined strings in general;
just as mandoc(1) is not intending to implement new languages,
but provide standard formatting for man(7) and mdoc(7) files,
whatever "standard" may mean in this context (sigh).
So move this to the right place.
noticed by deraadt@
|
|
Use non-breaking spaces to reduce the number of arguments.
This now formats correctly with both groff(1) and mandoc(1).
ok jmc@ sobrado@
|
|
instead, .It is required. Thus, move .Pp and text before the .Bl,
and remove the .Pp altogether where it is not needed.
Syntax errors found by mandoc(1), also required to fix the mandoc build;
feedback and ok jmc@, and sobrado@ also supports the direction.
|
|
syntax errors found by mandoc(1), also required to fix the mandoc build;
feedback and ok jmc@ and sobrado@
|
|
also required to fix the mandoc build.
"fine. even if mandoc goes nowhere, it has found some bugs ;)" jmc@
ok sobrado@
|
|
indicator". Even groff(1) does not in general seem very well-behaved
with respect to it, and it is not clear what advantage it might have
compared to '\"', the good old "beginning of comment" escape sequence.
Regarding the case at hand, it is breaking the mandoc(1) build,
and i checked that we get no output change from groff(1).
ok jmc@
|
|
Syntax errors found by mandoc(1), also required to fix the mandoc build.
ok jmc@
|
|
|
|
|
|
|
|
|
|
|