Alphabetize the "Who's Who" list.
This commit is contained in:
Nik Clayton
parent
9906e5666d
commit
6895e948d5
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=9420
2 changed files with 56 additions and 56 deletions
|
|
@ -19,7 +19,7 @@
|
|||
</author>
|
||||
</authorgroup>
|
||||
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/articles/committers-guide/article.sgml,v 1.65 2001/05/12 02:07:27 obrien Exp $</pubdate>
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/articles/committers-guide/article.sgml,v 1.66 2001/05/12 08:07:35 obrien Exp $</pubdate>
|
||||
|
||||
<copyright>
|
||||
<year>1999</year>
|
||||
|
|
@ -516,11 +516,11 @@
|
|||
</itemizedlist>
|
||||
|
||||
<para>You'll almost certainly get a conflict because
|
||||
of the <literal>$Id: article.sgml,v 1.66 2001-05-12 08:07:35 obrien Exp $</literal> (or in FreeBSD's case,
|
||||
of the <literal>$Id: article.sgml,v 1.67 2001-05-13 15:44:20 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.66 2001-05-12 08:07:35 obrien Exp $</literal> line, leaving the original
|
||||
<literal>$Id: article.sgml,v 1.66 2001-05-12 08:07:35 obrien Exp $</literal> line intact).</para>
|
||||
the second <literal>$Id: article.sgml,v 1.67 2001-05-13 15:44:20 nik Exp $</literal> line, leaving the original
|
||||
<literal>$Id: article.sgml,v 1.67 2001-05-13 15:44:20 nik Exp $</literal> line intact).</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
|
|
@ -1043,6 +1043,15 @@ docs:Documentation Bug:nik:</programlisting>
|
|||
</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.bde;</term>
|
||||
|
||||
|
|
@ -1093,6 +1102,21 @@ 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> or
|
||||
<filename>src/release/doc/*</filename>,
|
||||
as appropriate). 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.obrien;</term>
|
||||
|
||||
|
|
@ -1133,30 +1157,6 @@ 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> or
|
||||
<filename>src/release/doc/*</filename>,
|
||||
as appropriate). 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.65 2001/05/12 02:07:27 obrien Exp $</pubdate>
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/articles/committers-guide/article.sgml,v 1.66 2001/05/12 08:07:35 obrien Exp $</pubdate>
|
||||
|
||||
<copyright>
|
||||
<year>1999</year>
|
||||
|
|
@ -516,11 +516,11 @@
|
|||
</itemizedlist>
|
||||
|
||||
<para>You'll almost certainly get a conflict because
|
||||
of the <literal>$Id: article.sgml,v 1.66 2001-05-12 08:07:35 obrien Exp $</literal> (or in FreeBSD's case,
|
||||
of the <literal>$Id: article.sgml,v 1.67 2001-05-13 15:44:20 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.66 2001-05-12 08:07:35 obrien Exp $</literal> line, leaving the original
|
||||
<literal>$Id: article.sgml,v 1.66 2001-05-12 08:07:35 obrien Exp $</literal> line intact).</para>
|
||||
the second <literal>$Id: article.sgml,v 1.67 2001-05-13 15:44:20 nik Exp $</literal> line, leaving the original
|
||||
<literal>$Id: article.sgml,v 1.67 2001-05-13 15:44:20 nik Exp $</literal> line intact).</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
|
|
@ -1043,6 +1043,15 @@ docs:Documentation Bug:nik:</programlisting>
|
|||
</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.bde;</term>
|
||||
|
||||
|
|
@ -1093,6 +1102,21 @@ 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> or
|
||||
<filename>src/release/doc/*</filename>,
|
||||
as appropriate). 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.obrien;</term>
|
||||
|
||||
|
|
@ -1133,30 +1157,6 @@ 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> or
|
||||
<filename>src/release/doc/*</filename>,
|
||||
as appropriate). 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…
Add table
Add a link
Reference in a new issue