- Add myself as a committer
- Add my PGP public key
- Add my author entity
- Add a news entry
Approved by: imp (mentor)
Differential Revision: https://reviews.freebsd.org/D12303
- Add missing quote in 'zfs set sharenfs' command
- Use root prompt in various places to reflect reality
- Add missing <userinput> tags
- Remove a useless 'zfs list' command
- Use sysrc instead of echo command
in <phrase> elements. The its:notranslate property can then be set on
these individual lines rather than a whole <screen> or <programlisting>.
Sponsored by: iXsystems
OpenSSH 7.3p1 which went into stable/10 after that, it doesn't feel like
we are ready for the RC phase just yet. So 10.4-BETA4 has been inserted
into the 10.4 cycle and the optional 10.4-RC3 de-schedule for now.
- Mark the start of 10.4-BETA4 builds as done.
- The 10.4-BETA3 set includes the BEAGLEBONE image again, so uncomment
its betarel2 entry.
- Announce 10.4-BETA3 and bump betarel2.vers to BETA3 accordingly.
Approved by: re (implict)
Subversion has been told to expand $FreeBSD$ version strings in source
files. This is good, evidently.
But we don't want it to expand version strings in examples, because then
the example will have an expanded version string with the version of the
current doc file, which is bad. The version number, not the doc file.
Or, well, maybe both, but the point here is the version number won't look
right.
So use the good and righteous $FreeBSD$ construct instead.
This is perfectly cromulent and there is nothing remotely ridiculous or
surreal about this at all. Lalala, I can't hear you.
version strings. This will prevent them from showing up in PO
translations and causing difficulties.
It has the unfortunate side effect that the entire element contents do
not appear in PO files. Most of these are elements are <programlisting>,
which are probably not translated often yet. At least one is a <screen>,
which might be more of a problem.
At this point, this is a workaround to make it possible for PO translators
to continue work without the ever- changing version strings creating
conflicts.
files. This is good, evidently.
But we don't want it to expand version strings in examples, because then
the example will have an expanded version string with the version of the
current doc file, which is bad. The version number, not the doc file.
Or, well, maybe both, but the point here is the version number won't look
right.
So use the good and righteous $FreeBSD$ construct instead.
This is perfectly cromulent and there is nothing remotely ridiculous or
surreal about this at all. Lalala, I can't hear you.
