Minor changes:

* bento -> origini
* reflect 4-stable & 5-current.

Submitted by:	James Housley <jim@thehousleys.net>
This commit is contained in:
Alexander Langer 2000-09-30 14:25:53 +00:00
parent cc2d2cb84b
commit d1affdab96
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=8051
2 changed files with 38 additions and 26 deletions

View file

@ -16,7 +16,7 @@
</author>
</authorgroup>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/articles/committers-guide/article.sgml,v 1.36 2000/08/23 20:36:53 ben Exp $</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/articles/committers-guide/article.sgml,v 1.37 2000/09/24 07:01:47 kris Exp $</pubdate>
<copyright>
<year>1999</year>
@ -511,11 +511,11 @@
</itemizedlist>
<para>You'll almost certainly get a conflict because
of the <literal>$Id: article.sgml,v 1.37 2000-09-24 07:01:47 kris Exp $</literal> (or in FreeBSD's case,
of the <literal>$Id: article.sgml,v 1.38 2000-09-30 14:25:53 alex 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.37 2000-09-24 07:01:47 kris Exp $</literal> line, leaving the original
<literal>$Id: article.sgml,v 1.37 2000-09-24 07:01:47 kris Exp $</literal> line intact).</para>
the second <literal>$Id: article.sgml,v 1.38 2000-09-30 14:25:53 alex Exp $</literal> line, leaving the original
<literal>$Id: article.sgml,v 1.38 2000-09-30 14:25:53 alex Exp $</literal> line intact).</para>
</listitem>
<listitem>
@ -1737,7 +1737,7 @@ docs:Documentation Bug:nik:</programlisting>
</question>
<answer>
<para>Usually two to three days.</para>
<para>Usually an hour or two.</para>
</answer>
</qandaentry>
@ -1827,10 +1827,10 @@ docs:Documentation Bug:nik:</programlisting>
<answer>
<para>First, go check
<ulink url="http://bento.FreeBSD.org/~asami/errorlogs/">http://bento.FreeBSD.org/~asami/errorlogs/</ulink>.
<ulink url="http://onigiri.FreeBSD.org/errorlogs/">http://onigiri.FreeBSD.org/errorlogs/</ulink>.
There you will find error logs from the latest package
building runs on 3-stable and 4-current.</para>
building runs on 3-stable, 4-stable and 5-current.</para>
<para>However, just because the port doesn't show up there
doesn't mean it's building correctly. (One of the
@ -1844,12 +1844,18 @@ docs:Documentation Bug:nik:</programlisting>
/bak/errors error logs from last complete 3-stable run
/bak/logs all logs from last complete 3-stable run
/bak/packages packages from last complete 3-stable run
/4/errors error logs from latest 4-current run
/logs all logs from latest 4-current run
/packages packages from latest 4-current run
/bak/errors error logs from last complete 4-current run
/bak/logs all logs from last complete 4-current run
/bak/packages packages from last complete 4-current run
/4/errors error logs from latest 4-stable run
/logs all logs from latest 4-stable run
/packages packages from latest 4-stable run
/bak/errors error logs from last complete 4-stable run
/bak/logs all logs from last complete 4-stable run
/bak/packages packages from last complete 4-stable run
/5/errors error logs from latest 5-current run
/logs all logs from latest 5-current run
/packages packages from latest 5-current run
/bak/errors error logs from last complete 5-current run
/bak/logs all logs from last complete 5-current run
/bak/packages packages from last complete 5-current run
</programlisting>
<para>Basically, if the port shows up in

View file

@ -16,7 +16,7 @@
</author>
</authorgroup>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/articles/committers-guide/article.sgml,v 1.36 2000/08/23 20:36:53 ben Exp $</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/articles/committers-guide/article.sgml,v 1.37 2000/09/24 07:01:47 kris Exp $</pubdate>
<copyright>
<year>1999</year>
@ -511,11 +511,11 @@
</itemizedlist>
<para>You'll almost certainly get a conflict because
of the <literal>$Id: article.sgml,v 1.37 2000-09-24 07:01:47 kris Exp $</literal> (or in FreeBSD's case,
of the <literal>$Id: article.sgml,v 1.38 2000-09-30 14:25:53 alex 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.37 2000-09-24 07:01:47 kris Exp $</literal> line, leaving the original
<literal>$Id: article.sgml,v 1.37 2000-09-24 07:01:47 kris Exp $</literal> line intact).</para>
the second <literal>$Id: article.sgml,v 1.38 2000-09-30 14:25:53 alex Exp $</literal> line, leaving the original
<literal>$Id: article.sgml,v 1.38 2000-09-30 14:25:53 alex Exp $</literal> line intact).</para>
</listitem>
<listitem>
@ -1737,7 +1737,7 @@ docs:Documentation Bug:nik:</programlisting>
</question>
<answer>
<para>Usually two to three days.</para>
<para>Usually an hour or two.</para>
</answer>
</qandaentry>
@ -1827,10 +1827,10 @@ docs:Documentation Bug:nik:</programlisting>
<answer>
<para>First, go check
<ulink url="http://bento.FreeBSD.org/~asami/errorlogs/">http://bento.FreeBSD.org/~asami/errorlogs/</ulink>.
<ulink url="http://onigiri.FreeBSD.org/errorlogs/">http://onigiri.FreeBSD.org/errorlogs/</ulink>.
There you will find error logs from the latest package
building runs on 3-stable and 4-current.</para>
building runs on 3-stable, 4-stable and 5-current.</para>
<para>However, just because the port doesn't show up there
doesn't mean it's building correctly. (One of the
@ -1844,12 +1844,18 @@ docs:Documentation Bug:nik:</programlisting>
/bak/errors error logs from last complete 3-stable run
/bak/logs all logs from last complete 3-stable run
/bak/packages packages from last complete 3-stable run
/4/errors error logs from latest 4-current run
/logs all logs from latest 4-current run
/packages packages from latest 4-current run
/bak/errors error logs from last complete 4-current run
/bak/logs all logs from last complete 4-current run
/bak/packages packages from last complete 4-current run
/4/errors error logs from latest 4-stable run
/logs all logs from latest 4-stable run
/packages packages from latest 4-stable run
/bak/errors error logs from last complete 4-stable run
/bak/logs all logs from last complete 4-stable run
/bak/packages packages from last complete 4-stable run
/5/errors error logs from latest 5-current run
/logs all logs from latest 5-current run
/packages packages from latest 5-current run
/bak/errors error logs from last complete 5-current run
/bak/logs all logs from last complete 5-current run
/bak/packages packages from last complete 5-current run
</programlisting>
<para>Basically, if the port shows up in