Steve Price isn't the [unoffical] maintainer of `src/bin'.
Steve says: "That's just plain wrong."
This commit is contained in:
parent
eff1349e39
commit
9c0b49da1f
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=9127
2 changed files with 8 additions and 32 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.56 2001/04/04 11:54:01 nik Exp $</pubdate>
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/articles/committers-guide/article.sgml,v 1.57 2001/04/05 20:34:32 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.57 2001-04-05 20:34:32 obrien Exp $</literal> (or in FreeBSD's case,
|
||||
of the <literal>$Id: article.sgml,v 1.58 2001-04-05 20:35:49 obrien 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.57 2001-04-05 20:34:32 obrien Exp $</literal> line, leaving the original
|
||||
<literal>$Id: article.sgml,v 1.57 2001-04-05 20:34:32 obrien Exp $</literal> line intact).</para>
|
||||
the second <literal>$Id: article.sgml,v 1.58 2001-04-05 20:35:49 obrien Exp $</literal> line, leaving the original
|
||||
<literal>$Id: article.sgml,v 1.58 2001-04-05 20:35:49 obrien Exp $</literal> line intact).</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
|
@ -1112,18 +1112,6 @@ docs:Documentation Bug:nik:</programlisting>
|
|||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>&a.steve;</term>
|
||||
|
||||
<listitem>
|
||||
<para>Steve is the unofficial maintainer of
|
||||
<filename>src/bin</filename>. If you have something
|
||||
significant you'd like to do there, you should probably
|
||||
coordinate it with Steve first. He is also a Problem
|
||||
Report-meister, along with &a.phk;.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>&a.brian;</term>
|
||||
|
||||
|
|
|
@ -19,7 +19,7 @@
|
|||
</author>
|
||||
</authorgroup>
|
||||
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/articles/committers-guide/article.sgml,v 1.56 2001/04/04 11:54:01 nik Exp $</pubdate>
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/articles/committers-guide/article.sgml,v 1.57 2001/04/05 20:34:32 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.57 2001-04-05 20:34:32 obrien Exp $</literal> (or in FreeBSD's case,
|
||||
of the <literal>$Id: article.sgml,v 1.58 2001-04-05 20:35:49 obrien 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.57 2001-04-05 20:34:32 obrien Exp $</literal> line, leaving the original
|
||||
<literal>$Id: article.sgml,v 1.57 2001-04-05 20:34:32 obrien Exp $</literal> line intact).</para>
|
||||
the second <literal>$Id: article.sgml,v 1.58 2001-04-05 20:35:49 obrien Exp $</literal> line, leaving the original
|
||||
<literal>$Id: article.sgml,v 1.58 2001-04-05 20:35:49 obrien Exp $</literal> line intact).</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
|
@ -1112,18 +1112,6 @@ docs:Documentation Bug:nik:</programlisting>
|
|||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>&a.steve;</term>
|
||||
|
||||
<listitem>
|
||||
<para>Steve is the unofficial maintainer of
|
||||
<filename>src/bin</filename>. If you have something
|
||||
significant you'd like to do there, you should probably
|
||||
coordinate it with Steve first. He is also a Problem
|
||||
Report-meister, along with &a.phk;.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>&a.brian;</term>
|
||||
|
||||
|
|
Loading…
Reference in a new issue