files to use 5.x syntax (I hope..)
Note: I suppose one might need to hack the hints file as well?
Submitted by: Mike Barcroft <mike@FreeBSD.ORG>, Bruce Mah <bmah@FreeBSD.ORG>
move the ID string from a pubdate element into a comment on the
grounds that this document doesn't change rapidly enough to require
that the ID string to actually be rendered in the output.
DESTDIR. This avoids redundant information in the path when DOCDIR
points to some directory that already implies (or specifies) a certain
language. This is the case with the web site, where the release notes
are already installed under a language-specific directory. This
behavior is not being made mandatory because it might still be useful
to install all the translations in one directory, such as during
testing, or in a hypothetical release notes archive. Furthermore, it
is not being made the default because that breaks consistency with
stuff under doc/.
Reviewed by: bmah
notes build. Instead of having doc.relnotes.mk make a guess, hardcode
quite a bit (but as little as possible) in Makefile.inc's sprinkled
strategicly throughout the tree. This has the advantage of actually
working properly (which is a Good Thing(tm)), and the disadvantages of
more files in the repository and more hardcoded paths (which are both
Bad Things(tm)).
Tadayuki OKADA <tadayuki@mediaone.net>.
New release notes: USER_LDT on by default (this entry is way overdue).
Add Abocom URE 450 to supported USB Ethernet devices.
version control information that is different from the rest of their
containing document (or at least other sections). For release notes
only, allow output of <sect1info><pubdate></pubdate></sect1info>
text, and add it to three sections of RELNOTESng where it's kind of
important ("What's New" in the release notes, "Supported Device" in
the arch-independent hardware list, and the processors section of the
alpha hardware list).
1. Everywhere I could figure out what driver supported a device or
class of device, there is now a cross-reference via a &man entity.
For cases where a driver has no manpage (and hence no &man entity),
we now at least give the name of the driver. For the most part,
this was done by examining driver manpages.
2. A number of devices which are i386-only are now marked as such,
determined by noting manpages or kernel source files in
architecture-specific directories.
3. Added hardware supported by the vpo(4), wl(4), awi(4), and bktr(4)
drivers, based on a read of the manpages.
The manpages and source files in question were taken from 4-STABLE,
(which is what was running on my off-net laptop at the time)
but at this level of detail, I don't expect there to be any appreciable
differences between 4-STABLE and 5-CURRENT.
