Remove the frames from some of the tables. Make some of the
<informaltable>s real <table>s, with a title (instead of putting the notional title in a <para> immediately before it. Add Bruce Mah to the Who's Who section for the Release Notes. Add Ruslan Ermilov to the Who's Who section as Mr mdoc(7).
This commit is contained in:
parent
72d0d0a0e3
commit
f9e2cffeab
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=9116
2 changed files with 80 additions and 36 deletions
en_US.ISO8859-1/articles/committers-guide
en_US.ISO_8859-1/articles/committers-guide
|
@ -19,7 +19,7 @@
|
|||
</author>
|
||||
</authorgroup>
|
||||
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/articles/committers-guide/article.sgml,v 1.53 2001/04/03 16:12:05 obrien Exp $</pubdate>
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/articles/committers-guide/article.sgml,v 1.54 2001/04/04 00:52:50 kuriyama Exp $</pubdate>
|
||||
|
||||
<copyright>
|
||||
<year>1999</year>
|
||||
|
@ -171,9 +171,9 @@
|
|||
there is no <filename>shazam</filename> module in the modules file, looks for a
|
||||
top-level directory named <filename>shazam</filename> instead.</para>
|
||||
|
||||
<para>Useful options:</para>
|
||||
<table frame="none">
|
||||
<title>Useful <command>cvs checkout</command> options</title>
|
||||
|
||||
<informaltable>
|
||||
<tgroup cols=2>
|
||||
<tbody>
|
||||
<row>
|
||||
|
@ -199,7 +199,7 @@
|
|||
</row>
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</informaltable>
|
||||
</table>
|
||||
|
||||
<para>Practical FreeBSD examples:</para>
|
||||
|
||||
|
@ -312,7 +312,7 @@
|
|||
<filename>shazam</filename> directory. For every file, the
|
||||
status is given as one of:</para>
|
||||
|
||||
<informaltable>
|
||||
<informaltable frame="none">
|
||||
<tgroup cols=2>
|
||||
<tbody>
|
||||
<row>
|
||||
|
@ -369,7 +369,7 @@
|
|||
<para>Useful options, in addition to those listed above for
|
||||
<literal>checkout</literal>:</para>
|
||||
|
||||
<informaltable>
|
||||
<informaltable frame="none">
|
||||
<tgroup cols=2>
|
||||
<tbody>
|
||||
<row>
|
||||
|
@ -426,7 +426,7 @@
|
|||
update</command> with care.</emphasis> The letter in front of
|
||||
each file name indicates what was done with it:</para>
|
||||
|
||||
<informaltable>
|
||||
<informaltable frame="none">
|
||||
<tgroup cols=2>
|
||||
<tbody>
|
||||
<row>
|
||||
|
@ -516,11 +516,11 @@
|
|||
</itemizedlist>
|
||||
|
||||
<para>You'll almost certainly get a conflict because
|
||||
of the <literal>$Id: article.sgml,v 1.54 2001-04-04 00:52:50 kuriyama Exp $</literal> (or in FreeBSD's case,
|
||||
of the <literal>$Id: article.sgml,v 1.55 2001-04-04 08:31:49 nik Exp $</literal> (or in FreeBSD's case,
|
||||
<literal>$FreeBSD<!-- stop expansion -->$</literal>) lines, so you'll have to edit
|
||||
the file to resolve the conflict (remove the marker lines and
|
||||
the second <literal>$Id: article.sgml,v 1.54 2001-04-04 00:52:50 kuriyama Exp $</literal> line, leaving the original
|
||||
<literal>$Id: article.sgml,v 1.54 2001-04-04 00:52:50 kuriyama Exp $</literal> line intact).</para>
|
||||
the second <literal>$Id: article.sgml,v 1.55 2001-04-04 08:31:49 nik Exp $</literal> line, leaving the original
|
||||
<literal>$Id: article.sgml,v 1.55 2001-04-04 08:31:49 nik Exp $</literal> line intact).</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
|
@ -533,9 +533,9 @@
|
|||
<para>shows you every modification you've made to the
|
||||
<filename>shazam</filename> file or module.</para>
|
||||
|
||||
<para>Useful options:</para>
|
||||
|
||||
<informaltable>
|
||||
<table frame="none">
|
||||
<title>Useful <command>cvs diff</command> options</title>
|
||||
|
||||
<tgroup cols=2>
|
||||
<tbody>
|
||||
<row>
|
||||
|
@ -549,7 +549,7 @@
|
|||
</row>
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</informaltable>
|
||||
</table>
|
||||
|
||||
<para>You always want to use <option>-u</option>, since
|
||||
unified diffs are much easier to read than almost any other
|
||||
|
@ -612,9 +612,9 @@
|
|||
<para>Commit with the <literal>commit</literal> or
|
||||
<literal>checkin</literal> command.</para>
|
||||
|
||||
<para>Useful options:</para>
|
||||
|
||||
<informaltable>
|
||||
<table frame="none">
|
||||
<title>Useful <command>cvs commit</command> options</title>
|
||||
|
||||
<tgroup cols=2>
|
||||
<tbody>
|
||||
<row>
|
||||
|
@ -629,7 +629,7 @@
|
|||
</row>
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</informaltable>
|
||||
</table>
|
||||
|
||||
<para>Use the <option>-f</option> option if you realize that
|
||||
you left out important information from the commit message.</para>
|
||||
|
@ -1145,6 +1145,28 @@ docs:Documentation Bug:nik:</programlisting>
|
|||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>&a.bmah;</term>
|
||||
|
||||
<listitem>
|
||||
<para>Bruce is keeper of the release notes
|
||||
(<filename>src/release/texts/*</filename>). If you commit a
|
||||
change that you think is worthy of mention in the release notes,
|
||||
please make sure Bruce knows about it. Better still, send him
|
||||
a patch with your suggested commentary for the release
|
||||
notes.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>&a.ru;</term>
|
||||
|
||||
<listitem>
|
||||
<para>Ruslan is Mr mdoc(7). If you are writing a man page and need
|
||||
some advice on the structure, or the markup, ask Ruslan.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>&a.committers;</term>
|
||||
|
||||
|
|
|
@ -19,7 +19,7 @@
|
|||
</author>
|
||||
</authorgroup>
|
||||
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/articles/committers-guide/article.sgml,v 1.53 2001/04/03 16:12:05 obrien Exp $</pubdate>
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/articles/committers-guide/article.sgml,v 1.54 2001/04/04 00:52:50 kuriyama Exp $</pubdate>
|
||||
|
||||
<copyright>
|
||||
<year>1999</year>
|
||||
|
@ -171,9 +171,9 @@
|
|||
there is no <filename>shazam</filename> module in the modules file, looks for a
|
||||
top-level directory named <filename>shazam</filename> instead.</para>
|
||||
|
||||
<para>Useful options:</para>
|
||||
<table frame="none">
|
||||
<title>Useful <command>cvs checkout</command> options</title>
|
||||
|
||||
<informaltable>
|
||||
<tgroup cols=2>
|
||||
<tbody>
|
||||
<row>
|
||||
|
@ -199,7 +199,7 @@
|
|||
</row>
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</informaltable>
|
||||
</table>
|
||||
|
||||
<para>Practical FreeBSD examples:</para>
|
||||
|
||||
|
@ -312,7 +312,7 @@
|
|||
<filename>shazam</filename> directory. For every file, the
|
||||
status is given as one of:</para>
|
||||
|
||||
<informaltable>
|
||||
<informaltable frame="none">
|
||||
<tgroup cols=2>
|
||||
<tbody>
|
||||
<row>
|
||||
|
@ -369,7 +369,7 @@
|
|||
<para>Useful options, in addition to those listed above for
|
||||
<literal>checkout</literal>:</para>
|
||||
|
||||
<informaltable>
|
||||
<informaltable frame="none">
|
||||
<tgroup cols=2>
|
||||
<tbody>
|
||||
<row>
|
||||
|
@ -426,7 +426,7 @@
|
|||
update</command> with care.</emphasis> The letter in front of
|
||||
each file name indicates what was done with it:</para>
|
||||
|
||||
<informaltable>
|
||||
<informaltable frame="none">
|
||||
<tgroup cols=2>
|
||||
<tbody>
|
||||
<row>
|
||||
|
@ -516,11 +516,11 @@
|
|||
</itemizedlist>
|
||||
|
||||
<para>You'll almost certainly get a conflict because
|
||||
of the <literal>$Id: article.sgml,v 1.54 2001-04-04 00:52:50 kuriyama Exp $</literal> (or in FreeBSD's case,
|
||||
of the <literal>$Id: article.sgml,v 1.55 2001-04-04 08:31:49 nik Exp $</literal> (or in FreeBSD's case,
|
||||
<literal>$FreeBSD<!-- stop expansion -->$</literal>) lines, so you'll have to edit
|
||||
the file to resolve the conflict (remove the marker lines and
|
||||
the second <literal>$Id: article.sgml,v 1.54 2001-04-04 00:52:50 kuriyama Exp $</literal> line, leaving the original
|
||||
<literal>$Id: article.sgml,v 1.54 2001-04-04 00:52:50 kuriyama Exp $</literal> line intact).</para>
|
||||
the second <literal>$Id: article.sgml,v 1.55 2001-04-04 08:31:49 nik Exp $</literal> line, leaving the original
|
||||
<literal>$Id: article.sgml,v 1.55 2001-04-04 08:31:49 nik Exp $</literal> line intact).</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
|
@ -533,9 +533,9 @@
|
|||
<para>shows you every modification you've made to the
|
||||
<filename>shazam</filename> file or module.</para>
|
||||
|
||||
<para>Useful options:</para>
|
||||
|
||||
<informaltable>
|
||||
<table frame="none">
|
||||
<title>Useful <command>cvs diff</command> options</title>
|
||||
|
||||
<tgroup cols=2>
|
||||
<tbody>
|
||||
<row>
|
||||
|
@ -549,7 +549,7 @@
|
|||
</row>
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</informaltable>
|
||||
</table>
|
||||
|
||||
<para>You always want to use <option>-u</option>, since
|
||||
unified diffs are much easier to read than almost any other
|
||||
|
@ -612,9 +612,9 @@
|
|||
<para>Commit with the <literal>commit</literal> or
|
||||
<literal>checkin</literal> command.</para>
|
||||
|
||||
<para>Useful options:</para>
|
||||
|
||||
<informaltable>
|
||||
<table frame="none">
|
||||
<title>Useful <command>cvs commit</command> options</title>
|
||||
|
||||
<tgroup cols=2>
|
||||
<tbody>
|
||||
<row>
|
||||
|
@ -629,7 +629,7 @@
|
|||
</row>
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</informaltable>
|
||||
</table>
|
||||
|
||||
<para>Use the <option>-f</option> option if you realize that
|
||||
you left out important information from the commit message.</para>
|
||||
|
@ -1145,6 +1145,28 @@ docs:Documentation Bug:nik:</programlisting>
|
|||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>&a.bmah;</term>
|
||||
|
||||
<listitem>
|
||||
<para>Bruce is keeper of the release notes
|
||||
(<filename>src/release/texts/*</filename>). If you commit a
|
||||
change that you think is worthy of mention in the release notes,
|
||||
please make sure Bruce knows about it. Better still, send him
|
||||
a patch with your suggested commentary for the release
|
||||
notes.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>&a.ru;</term>
|
||||
|
||||
<listitem>
|
||||
<para>Ruslan is Mr mdoc(7). If you are writing a man page and need
|
||||
some advice on the structure, or the markup, ask Ruslan.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>&a.committers;</term>
|
||||
|
||||
|
|
Loading…
Reference in a new issue